I am having trouble with one post in my blog. It is the most recent post from today.
When I run my blog locally, everything works fine for all posts. When I publish my blog, the most recent post from today acts weird when I click into it. The rest of the blog posts appear to be fine.
When I click on the post I made today, it comes up garbled. It looks like this. IMG_7438 · CleanShot Cloud If I go back, look at an older post, then return to the post for today, it loads correctly.
Sometimes when the post loads, the graphic doesn’t show up. It gives me a box with a question mark, like this. IMG_7439 · CleanShot Cloud Remember everything loads correctly locally, just not when it is posted.
Once posted, when I click on related items associated with this post, they don’t show up! If I look at older posts and click on related items there, they load fine.
The funky part is that when I run things locally, everything is fine. I only have this problem when the blog is posted to my server.
This appears to be a server-based issue. I am with Chilidog web hosting, running PHP 8.4.
I have republished all files to my website, but the problem persists.
Does anybody have an idea where the problem lies? Thanks in advance for your help!
I think I am able to get graphics to load by changing the size of the graphic.
When it comes to the related items from the entry not working, I found my problem. I am not running the site in SSL mode, but it was set to upload to the site to “https://…”. . I took the “s” away and am posting to regular FTP, but when a related item is clicked, it is still throwing an https:// in front of the name, which causes it to not load.
If you want to have some fun with this, after you look at the most recent blog entry, on the right, under related items, you will find “Logical and Historical Reasons To Believe Your Bible”. If you click it, nothing happens. But if you go to the URL line, highlight it, and hit the enter key, the related post loads fine.
I reached out to chilidog this morning and hope to have SSL activated for the site today. I didn’t activate it before because christtoourculture.com is only for testing purposes. When the site is done, I will replace christ2Rculture.com, which is the current public version designed with RW.
this is a strange one, it’s actually something I’ve never seen before…
It looks like the issue is that when the browser is trying to fetch the CSS and JS files, those requests aren’t being allowed to complete properly by the server. Instead of returning the files, the server is responding with a non-standard “449” error, which basically means “the server has refused the request for some reason.”
Because the files do load when you visit them directly, it suggests nothing is wrong with the files themselves, but something on the server is blocking or modifying the requests when they’re loaded as part of the page. That could be down to security rules, SSL settings, or something similar on the hosting side.
Another odd thing I’ve noticed is that if I first open any other blog post and then navigate back to the first post, everything works as expected.
I think all of this points to a server-side issue rather than anything in Elements or the project itself. My best guess is that something on the server, possibly security rules or SSL configuration, is causing those 449 responses. Would you be able to ask your host if they can see why the server is returning 449 for those CSS/JS requests when they’re loaded as part of this page Christ 2R Culture - Sermon Archive
They made some adjustments on their end. It appears to work great! Thank you for helping me problem-solve this!
I will be back on the forum later today with more questions (but they will all be much easier than this one!
I’ve made some adjustments to your NGINX settings in cPanel. Give it another go and see if it’s working now. (restart your browser or reset caches/try a different browser if needed)
@ben
By the way, I’m experiencing exactly the same issue.
It always affects only the first blog post. All subsequent posts work fine. As soon as I add another blog post, the previously affected one is displayed correctly again.
I don’t host my sites with Chillidog — I’m using all-inkl.com.
Possible adjustments via all-inkl.com are not an option, as this is shared hosting.
My current workaround is to always have a “fake” Markdown file that is displayed first, and then set the pagination offset to 1.
@Pegasus, I am with Chilidog web hosting. I contacted them. Below is their response, and it took care of the first-blog-entry problem on my site.
I’ve made some adjustments to your NGINX settings in cPanel. Give it another go and see if it’s working now. (restart your browser or reset caches/try a different browser if needed)
@Pegasus, Sorry for the needless reply. I responded to your post first thing this morning and had either skipped or not seen your middle comments. Moral of the story is… don’t respond until you have your coffee.
I think you’re issue is likely to do with how you have the individual pages setup (if I remember correctly you’re manually creating each page for the CMS items).
Can you send me the latest project so I can do some further testing?
