Raul P.

You deleted the cache files for the css and js files, but not for the html pages. Check if your hosting is caching your page, or if some other plugin is doing it.

If you delete the css js files and don’t delete the page cache, the page will still be pointing to the deleted files.

Thank you for reporting.
The code is being minified by PHP Minify and it looks correct to me.

What does not look correct is your original code, are you sure that is supposed to look like that?

Your original indented code:

cb.cmd.push(function() {
    cb({ 
        playerId: "1c29db-b110-4350-9460-5346a3b47" }).render("612e04d63a69bed46a146c9a4") 
    })
	
	};
	});
}

where

};
});

is incorrect, or perhaps you did not post the whole code.
This is either added incorrectly, or there should be some code before.
For every } there should be an { usually, as well as for ( and ).
The semicolon, can be replaced with a line break, in some cases too.

There is a bug with your theme development, or the developer that edited it, forgot to change the query string.

Currently, you would need to exclude all files under your theme directory by adding /themes/yolanddesign/ to the css and js ignore list, however, the real reason why this happens, is that your theme css and js files change the query string on every pageview.

For example:
https://bramleyappledesign.co.uk/wp-content/themes/yolanddesign/fw/js/swiper/swiper.css?rnd=2142481582

The ?rnd=2142481582 changes on every time you refresh the page, and this is wrong.
Tell your developer to remove the rnd query from the enqueued assets, so that they can remain static and not change on every pageview (do not install another plugin to remove the query strings… they guy added it with code, so he needs to edit it again, or ask the theme author).

That’s probably some server setting, not the plugin.
But to my knowledge, cache enabler uses gzip to compress the cache files, so check if you have enabled that option.

If you have dynamic css or js files, those keep changing every time it’s minified and it’s a new file. You would need to manually check which file keeps changing and exclude it from minification.

It’s also possible that all your pages have different css or js files, in which case, you will need a set of minified files per page. You can disable merging and see if it helps.

It’s also safe to periodically delete the cache directory, as it will be rebuilt.

@mike8040 if you change some css file, you must purge all caches, always, regardless of using FVM or not, else you won’t see those changes consistently.

Files don’t require a query string. Query strings should not exist on static files.
If the file contents changed, FVM will rename it differently. The filename, is an hash of the code it was merged. But the minification is cached, to speed things up, that is why you need to purge the caches after modifying files.

The file renaming, is already the cache busting mechanism.

What problem exactly are you facing?
It sounds like you simply did no purge the caches properly.

—

@devopti the files are not deleted after 24 hours. If you don’t have the immediate purge enabled, it will only delete files older than 24h, at the time of the purge.

Minified files are static files with dynamic url’s, which may disappear anytime.
FVM needs to be able to purge the page cache, else your page caching is pointing to the wrong files. Whenever there is a FVM cache purge, you need to purge the HTML cache globally.

If you wan to increase the limit, then you can edit the functions.php file on line 540 and replace 86400 with the desired amount of seconds.

But hold on for that, there will be an update in a few days and I will extend this to 7 days for broader compatibility.