Raul P.

You would need to use a compatible cache plugin, or a hosting that is supported by the plugin.

It will depend on how the page cache is running and for how long it’s valid.

When you update a plugin, theme, or as needed, the code changes so the cache needs to be regenerated and the file names will change. If the file names were not changed, the updates would not be reflected on your users browsers, or it would be cached on the CDN and errors would occur.

The issue of missing CSS/JS files means, you have purged FVM or the daily maintenance to delete expire files ran, but page cache was not cleared. If you do not clear page cache after deleting fvm generated files, they will result in 404 errors.

FVM tries to auto purge several hosting providers and cache plugins, however, if your hosting also does page caching in-between and FVM cannot purge it, that may be the reason for the situation to happen.

Please ensure that whenever you purge FVM, you also purge your page caching.

It’s compatible with PHP 8 and WP 5.9. Thanks

Thanks, this will be fixed on the next update.

It will depend on how the page cache is running and for how long it’s valid.

When you update a plugin, theme, or as needed, the code changes so the cache needs to be regenerated and the file names will change. If the file names were not changed, the updates would not be reflected on your users browsers, or it would be cached on the CDN and errors would occur.

The issue of missing CSS/JS files means, you have purged FVM or the daily maintenance to delete expire files ran, but page cache was not cleared. If you do not clear page cache after deleting fvm generated files, they will result in 404 errors.

FVM tries to auto purge several hosting providers and cache plugins, and WP Cloudflare Super Page Cache is supported, so there should be no issues. However, if your hosting also does page caching in-between, that may be the reason for the situation to happen.

The data is not serialized, it’s json encoded.
You can access it as an array, inspect the keys and save it’s settings accordingly.

// get settings
$fvm_settings = json_decode(get_option('fvm_settings'), true);
// your changes here
$fvm_settings['some_key'] = 'value';
// resave
update_option('fvm_settings', json_encode($fvm_settings), false);

If you are doing this, please ensure it doesn’t check on every pageview, else you will stress the database. Use transients perhaps, or some “done” field, somewhere else as a control.

Doesn’t seem to have any problem then.
https://www.xml-sitemaps.com/validate-xml-sitemap.html?op=validate-xml-sitemap&go=1&sitemapurl=https%3A%2F%2Fvaporbros.net%2Fsitemap_index.xml&submit=Validate+Sitemap