December 30th, 2018 at 14:30 #72176
Hello dear folks from Cryoutcreations !
This morning I made an update from 220.127.116.11 to 18.104.22.168, and there was something terribly wrong with the new version. The homepage (styled with Content Views to a multi-column-layout) looked like it totally missed out in CSS, all columns pressed in a very tight one on the left side of the screen, while the article page showed in a rather rudimentary fashion. I had to do a rollback to 1.4.1 from subversion, now everything is back to how it was.
Cheers from Cologne,
December 31st, 2018 at 16:42 #72244
- This topic was modified 4 years ago by tomppa28. Reason: Just put in the correct versions
That sounds like entire styling files missing. Since you’re using a caching plugin, I suggest clearing the cache after performing updates to ensure WordPress is loading the correct files.January 1st, 2019 at 15:17 #72275
thank you for having taken the time to reply. And a very happy and successful new year to all the good folks from Cryout Creations !
As for my problem, I don’t think the cache was the problem. 1st of all:
I don’t have a caching plugin installed, so this could only be the Apache-cache. I emptied that, the problem persisted. To verify again, I redid the update today – exactly the same problem.
Website: baugelitt.euJanuary 1st, 2019 at 19:43 #72279
Happy New Year!
Your site has the Autoptimize plugin actively caching and minifying the entire site.
The screenshot confirms that styling fails to load (most likely due to cached resources conflicting with update changes).January 1st, 2019 at 22:50 #72286
OK, I installed the update, emptied the Autoptimize-cache and retried: Same result. Then I deactivated the complete plugin and everything worked like a charm. To be sure, I re-activated it and, as expected, the problem reappeared. As I would like to keep the plug-in, I had to go through the options and finally found that deactivating the option “optimize CSS code” finally did the trick. Thank you for your help!January 3rd, 2019 at 18:15 #72340
If that functionality used to work before, it should continue working even after the update (after a successful cache reset).
Have you updated anything else beside the theme at the same time?
The topic ‘Problem with update to 1.4.2’ is closed to new replies.