Hello there,
I can see that it is a cache issue of your website. You are removing the theme version from the query string of the style.css (it should be 1.7.0 but it is completely removed in your site).
If you clean your cache you can find the style css asset correctly updated and everything will work as expected to be.
When a theme update occours, we always change the style.css query string to avoid these issues to our customers, but if you have a particular configuration with a cache plugin, it is up to you to flush the cache when theme or plugins are updated (generally cache plugins add a backend notice asking you to flush the cache because a theme or plugin was installed, disinstalled or updated).
Thank you very much, I excluded the file type .css in the cdn, the problem was solved
Hello Francesco.
I tried all your advices but nothing. Before updating the theme I disabled WP Optimize for the site cache then I updated and the failure occurred immediately. I don’t use cdn other than Jetpack for the images. As soon as I brought the theme back to 1.6 everything went back to normal. It seems that 1.7 is incompatible with WP 5.8.1 otherwise I don’t know how to justify such behavior. The problem is that the theme is now not updatable.
After many attempts lasting a whole day I have proof that Proteo 1.7.0 creates a conflict with Worpress 5.8.1 and the latest stable version of Woocommerce. I say this because before updating Proteo I purged the cache and disabled it along with the minification of css, javascript and html. I tried all sorts of changes but as soon as the new update comes into operation it changes the layout of the site and there isn’t way to restore it. The products to be 4 per row become 1 below the other in a single column and the same happens for related products. Entering Customize Appearance the only thing you can do is to set 2 products per row since 3 returns the layout to be in a single column. The same for related products. I cleaned the browser cache, the site cache and anything that could be dated but nothing. I don’t use cdn. As soon as I return to version 1.6.0 everything is fine. Tell me if this is not incompatibility?! Before Proteo I had Storefront and have updated it several times but it has never created anything like this. Now I have a non-updatable theme and the obligation to abandon it in spite of myself for something stable. It is possible to have help, please? Thank you.
You have to clean the cache and minimized scripts and css AFTER Proteo is updated, not BEFORE.
If you do this before you freeze all your scripts to a previous version.
Steps:
– enable all your wanted cache plugins
– update Proteo
– disable options to remove query strings from scripts
– flush cache
– rebuild all minimized css
This will solve all your issues. No issues with WordPress or WooCommerce. I can assure it to you
Thanks to your kind advice I have resolved. Now all it is fine.
We appear to have the same issue – just upgraded to Proteo 1.7.1 and suddenly the site has an abnormal layout: what should be from 5 items per row to all items in a single column.
We have cleared the server side caching, but for any user who has visited the site before there appears to browser caching of Proteo style.css which causes the issue. If they Ctrl+F5 they get a new version of the style.css and everything is fine, but I that isn’t really a solution.
There appears to be something odd with the version string for style.css which shows as
<link rel='stylesheet' id='parent-style-css' href='https://www.isle20.com/wp-content/themes/yith-proteo/style.css?ver=5.8.1' type='text/css' media='all' />
This is the version number of wordpress not the version number of Proteo and obviously it didn’t change when I updated Proteo – which is why the browsers are not fetching the new version of the file.
Yes we are using a child theme of Proteo but there is nothing in it’s style.css and it is correctly loading with version number 1.7.1 `<link rel=’stylesheet’ id=’yith-proteo-style-css’ href=’https://www.isle20.com/wp-content/themes/yith-proteo-child/style.css?ver=1.7.1′ type=’text/css’ media=’all’ />
`
Any suggestions?
example impacted page is https://www.isle20.com/books/
Hello there, this is how I see that website.
So the issue is related to browser cache.
Please check if you have a plugin to manage this and resource query strings (versioning). Or if you are using cloudflare where you can manage this too
