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://www.ads-software.com/support/topic/wpo-minify-errors-part-2/

Cheers
Tony

Nice one Venkat.

Keep up the good work, in our opinion, on the fastest and best cache & minify WordPress plugin.

We don’t compare using speed test sites…….We use real world browser response figures.
WP-Optimize beat WP-Rocket in both cache and Minify in our tests a couple of years ago. Now that speaks for itself.

Tony.
Data Centre Administrator.

Hi Venkat,

We raised this issue in March of this year. Personally, we have a workaround and no longer disable WP-Optimize minification whilst performing maintenance tasks, so as already stated, these 404 errors no longer happen on our servers. However, as this issue has recently been reported by someone else on my initial thread which I raised in March, I have checked on my test server and sure enough the problems still exist when minification is enabled for a couple of days and then disabled.

During March, all minify 404 errors were re-directed to the respective homepages using 302 redirects.
Fortunately we have retained a portion of the Apache logfile and you are welcome to view it to see the information that you requested above. Please note that the logfile shows 302 instead of 404.

https://www.backtothemovies.com/wpo-minify.log

Also the static file headers ARE enabled, but are set to:

# HTML
ExpiresByType text/html “access plus 0 seconds”

Thanks
Tony

• This reply was modified 2 years, 6 months ago by ittone.

One further note that I failed to answer.

I’m afraid I have to disagree with part of the following statement:

“Besides, if plugin is deactivated it means that there is some significant change is going to happen on the site. In that case the already cached files become obsolete.”

By any remote site attempting to access cached minified files (no matter from what server/workstation in the world) and those files have been deleted from the host server, then those files have NOT become obsolete UNTIL such time as the source server/host cache files have been purged.

As I stated in my previous reply, this could be anywhere between three days to three months as I have already proven during our initial investigations several months ago.

Today, we have NO minification 404 cache errors on any of our customer sites as,
1: We have not disabled the minification of JS and/or CSS files for four or more months.
2: All remote CDN, browser caches etc. have flushed their cache at some point during this time spell.

Thanks
Tony.
Data Centre Administrator.

Hi Guys,

In answer to your question “Are you using a CDN? If so, which one?”

The answer is NO……But, the majority of visitors attempting to access pages which have been deleted (de-activated expired minify cached files) seem to be mainly visiting from that type of network.
Good example: google.com bots where the majority of these 404 errors originate from, closely followed by other BOTS….We have also seen many examples of human visitors presumably using their browser cache info to access….now…non existent cache.

So, we have no way of deleting cache files outside of our control.

As for not being able to distinguish between a temporary and permanent deactivation, how about upon installation/upgrade, a temporary minify reference file was created in the wp-optimize directory or for that matter, the cache directory. If a de-activation of minification was made the file being present prevents the deletion of the minify cache files.
Upon de-installation of the plugin, you could provide an option to retain or totally delete the minification files, stating the consequences of doing so if deleted.
OR
Just retain the minified cache files upon deletion of the plugin.

For users of your plugin, including ourselves who would at some point experiment with different minification plugins, say for several days would all see these 404 file not found errors and as us have been presented with thousands of these errors per day on a continuous basis until the remote servers cache expires. In many cases this is seven days, but we have seen one month and even three months attempted access to expired cache files.

Hope this helps, as it certainly would as a fix.

Thanks
Tony

Harshad.

I have changed the staus of this thread back to unresolved. Please see the above two previous posts.

Cheers
Tony

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 2 years, 6 months ago by ittone.
• This reply was modified 2 years, 6 months ago by ittone.

Hi

Have your development team updated you on my findings yet please?

Tony

Thanks, I will look forward to what they have to say.

Tony

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

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 3 years ago by 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.”

@celebtemple

Have a read of my post..Same problems, but try Raul’s suggestions which did not work for me, but may for you.

https://www.ads-software.com/support/topic/v3-0-3-08-not-creating-cache-files/

• This reply was modified 4 years, 2 months ago by ittone.

Thanks for the reply Raul

Sorry, the boundary has now been crossed from my UNIX/Linux technical skills to that of yours of a programmer……I know when to hand over to another department. LOL

I will contact you via fastvelocity.com

Cheers.

Hi Raul
Thanks for your help to date.
These are the settings that are enabled. If not mentioned, then they are disabled.

Purge Minified CSS/JS files instantly
Preserve settings on uninstall

Enable HTML Processing
Cleanup Header

Enable CSS Processing
Remove “Print” CSS files
Merge Fonts and Icons separately

Enable JS Processing

Multiple variations of these settings produce NO minification.
—————————————————-

Do you have the wp_fvm_logs and wp_fvm_cache tables when the plugin is enabled? YES

If yes, are they being populated as you browse the site and it starts caching files? NO

Do you get anything being generated on the css/js logs, in the status page on FVM (refresh to check) when browsing the site anonymously? No

When you disable JS and CSS processing, and then enable HTML minification, do you see the code getting minified for anonymous users? NO

All plugins had been disabled whilst I was testing, other than FVM.

Either way, it seems to be specific to your server or some other plugin…….. Not producing minified files on a Litespeed server NOR on an Apache server.

However as stated before. Version 2.8.9 works fine on this site, but v3+ DOES NOT.

Cheers
IT Tone

• This reply was modified 4 years, 2 months ago by ittone.
• This reply was modified 4 years, 2 months ago by ittone.
• This reply was modified 4 years, 2 months ago by ittone.
• This reply was modified 4 years, 2 months ago by ittone.
• This reply was modified 4 years, 2 months ago by ittone.