2 issues on new version.

Hi,

For 1,

a) check the status page under the logs and ensure that the css file path is correct. You may be merging some other file if the file path is incorrect.

b) if FVM cannot pen the file locally, it will fetch it via http. In that case, it may be cached on cloudflare, some other cdn, or on your server cache.

If you copy paste the file path for the css file being merged into the browser, make sure it’s showing the correct file.

Also, if your server has a remote disk, the file code may be cached on the server. Some hosting services do this (it’s explained in the HELP tab). They cache files somewhere, to prevent a round trip to the remote storage, and even when you delete the file, sometimes they are still readable as if you never deleted them.

When you purge ALL on FVM, it does 3 things.

It deletes the FVM public files.
It purges the individual file cache on the database (each file that is downloaded or merged is cached here, and reused later to merge and generate the main file).
It purges your cache plugin and hosting (if supported… you may need to do it manually depending on what you use).

So it’s straightforward… open phpmyadmin and look for the wp_fvm tables.
They will be empty right after you purge ALL.

Then as it detect each file to merge, it will reopen them from the disk or via HTTP and save them there minified.

I the stored code there is not changing, look at the meta information column and see if it was downloaded or opened locally.

Most likely, it’s cache somewhere.
You may be editing the physical files but due to server or cdn cache, FVM is still only able to read the old file.

Make sure to purge all possible caches, including CDN, cloudflare, sucuri, server page cache, OPCache, disk cache, REDIS, Memcached, etc.

Usually restarting the server will purge most of those server caches, but not only.
In that case, contact your hosting.

FVM cannot be reading a file that no longer exists, or has been changed.
You can try to rename the original file and see if FVM can still find it… which would be impossible, unless PHP, Nginx, Apache, CDN or whatever is caching the file information somewhere.

—-

2. This is another evidence that cache is stored somewhere and you are not purging it properly.

If you have deselected the settings AND deleted the domain name in that domain field, FVM cannot possibly have any information regarding the domain to replace it.

The only way that could happen, would be if wordpress is still reading the old settings from the database.

Several hosting providers cache database requests as well, which is just another way to make things seem faster.

Disable your OPCache settings and all caching on the server and try again.
If it works without that cache, then you have your answer.

Your hosting is caching too much data and it prevents settings from changing.
I have seen this recently on siteground, not only with FVM but with several other plugins.

Contact your hosting and tell them to disable and purge all caches, as well as any cdn or proxy service that routes your site through that (varnish for example, or cloudflare).

• This reply was modified 4 years, 1 month ago by Raul P..

NO, it is not solved.

And “CDN URL” in your settings simplly doesn’t work for my CDN.

Please can you load every minified css and js the WordPress way? Thus my CDN can featch them normally.