@ittone Could you please try to purge minified files from WP-Optimize > Minify and check if you still get 404 errors?
Thread Starter
ittone
(@ittone)
Harshad
I administer websites.
I did write above:
“cache errors even several days after first disabling the minification option and then completely deleting the plugin altogether.”
@ittone Have you performed a conflict test yet?
Try deactivating all plugins except for WP-Optimize and see if it is resolved.
If so, reactivate each plugin one at a time until you find the culprit. You can check for the issue between activating each plugin, so you can see which one is causing problems.
Please let us know your findings.
Thread Starter
ittone
(@ittone)
Please bear with me for a day or two on this one.
The minify cache 404 errors are also appearing with FVM when enabled and then deactivated for several days.
Does clearing the wp-optimize minify cache clear the server’s OPCache???
If it does not….that could be part of the problem.
Tony
-
This reply was modified 4 years, 2 months ago by
ittone.
@ittone No it doesn’t clear the OpCache, I’ll report this issue to our development team for further investigation, so that it can fixed in future release
Thread Starter
ittone
(@ittone)
Hi Harshad.
OK, we have at last got to the bottom of the missing minification 404 errors.
We occasionally have the need to de-activate plugins to carry out maintenance of which wp-optimize is one of those plugins.
Once wp-optimize is de-activated all wp-optimize cache and minification and temp transient files are deleted.
Why on earth are minification files deleted upon a temporary de-activation?
CSS & JS files are by default held in a browser’s/search engines cache for upto twelve months, so when the plugin is re-activated the cached css and js files no longer exist on the server. This produces absolutely thousands of wpo-minify/xxx 404 errors per day from these non-existent cache files and can still produce these 404 errors for months on end even after re-activation.
Surely no plugin should act in this manner.
Delete the cache and minify directories when the plugin is deleted, but my goodness it has raised a few blood pressures here when just de-activating.
Please inform the plugins author of this oversight.
Kind regards
Tony
@ittone Thanks for sharing more information on this, I’ll share the same with our development team.
Thread Starter
ittone
(@ittone)
Thanks, I will look forward to what they have to say.
Tony
Thread Starter
ittone
(@ittone)
Hi
Have your development team updated you on my findings yet please?
Tony
@ittone No we are still working on this
I am having a similar issue with css disabled and lots of wpo minify 404 errors. Is this issue going to be resolved? I don’t understand why this issue is marked resolved on this page when it seems to be an ongoing serious bug.
Thread Starter
ittone
(@ittone)
I confirm that this issue I raised 6.5 months ago, has still NOT been resolved.
The minification files JSS and CSS are still being deleted upon a temporary de-activation of the minify plugin. This should NOT be the case and is still causing us problem/s for each and all of our clients, processor activity, and bandwidth issues.
Just do not delete the minify files upon de-activation.
Thanks
Tony.
Data centre administrator.
-
This reply was modified 3 years, 8 months ago by ittone.
-
This reply was modified 3 years, 8 months ago by ittone.
Thread Starter
ittone
(@ittone)
Harshad.
I have changed the staus of this thread back to unresolved. Please see the above two previous posts.
Cheers
Tony
Thread Starter
ittone
(@ittone)
Webgalway.
You will find a continuation of this thread on the link below.
A fix is in sight and I am informed that will be released in the October plugin update.
One point to mention is that if you are using a .htaccess file (or equivalent) change the text/HTML to the following for the time being.
# HTML
ExpiresByType text/html “access plus 0 seconds”
https://ww.wp.xz.cn/support/topic/wpo-minify-errors-part-2/
Cheers
Tony
