CSS frequently hitting 404 errors
-
Hi,
We have an ongoing issue with quite a number of our sites now, whereby the CSS will often 404 and so the site looks awful.
We’ve tried tinkering with the settings across most of them, but it will randomly break and our customers will notify us that the site looks messed up. A quick look shows the CSS file(s) have hit a 404. A quick purge of the cache and everything goes back to normal.
Example before purging the cache – https://prnt.sc/1s1uylp
What we’re really struggling to figure out why this keeps randomly happening? All of our sites have automatic updates turned off, and the majority of them have no admin access to the customer, so in theory once the site has had its cache purged, nothing should change after that so A) why does the cache need rebuilding if the site hasn’t changed at all, and B) why is it failing?
Any ideas what we should be looking for, or why the CSS wouldn’t get refreshed correctly?
Thank you
The page I need help with: [log in to see the link]
-
We have kinda the same problem with many clients lately, including our own website. The only way to fix this seems to go to WordPress LS Cache plugin > Toolbox > Choose “Empty all cache”, not “Purge all”. This seems to help the issue of randomly 404 errors of .css files breaking the website.
I don’t get the difference. I’m sure from a technical standpoint there is a reason for this, but from user perspective its confusing.
Same goes for the solution mentioned above, what is the difference between:
“Purge All and Purge All – CSS/JS Cache” or;
“Purge All”?When I want to “Purge All Cache”, I guess I would like to purge all cache, not “Purge All Cache (except for the ultrasecret hidden for CIA CSS/JS)”.
Most WordPress users, I suspect +50%, are not very technical driven users and don’t see the difference. It it hard to explain all the different options in purging.
Ofcourse open to idea’s!
- The topic ‘CSS frequently hitting 404 errors’ is closed to new replies.
