Hello @jackmac71
I do see that you have the WP Rocket plugin, which you have set up to do heavy processing on the CSS and JS, which might affect workflows if the plugin’s configured incorrectly.
Could you please give it a shot with the plugin completely disabled in order to confirm where the issue is coming from?
Thanks.
Hi Eduard,
thanks for your ultra fast response.
I deactivated wprocket completly and the issue is gone, after activating wprocket again, the issue is back. Now we know what it causes, but how can I solve this?
The issue is new, before the last blocksy update the top to scroll button works fine.
Best regards
Hello @jackmac71
I can assure you that we haven’t touched the scroll to top button/code for the past 10+ updates. There’s no way an update could’ve changed its behaviour.
It is a matter of WP Rocket being configured incorrectly and/or not clearing its cache properly to reprocess the CSS/JS files.
But actually, we do not recommend processing at least Blocksy’s CSS and JS files at all, since they’re already optimised in the same way all caching plugins do it. They’re already minified, combined where it makes sense and loaded on demand whenever a feature is need.
We have a general guidelines article here – https://creativethemes.com/blocksy/docs/troubleshooting/the-case-of-over-optimising-your-website/ – that has some tips on how you may want to handle Blocksy’s files.
Hope this helps!
Thanks.