Raul P.

This was added. Thanks

I am not seeing any issue with the Disable CSS Link Preload, or Disable JS Link Preload.
Perhaps you are seeing a page cache, and that is why it looks as if it’s not doing anything?

You can confirm this by changing clearing the cache on FVM, then look at the file names.
/wp-content/cache/fvm/min/XXXXXXXXX-YYYYYYYYYYY.css WHERE XXXXXXXXX will be a number, that must be different from the previous time you purged the cache.

Whenever you purge FVM, this XXXXXXXXX number will change, so if you don’t see it changing, you are seeing a page cache (hosting, cdn, plugin, etc).

The header cleanup is intended. A lot of plugins add preconnects and other hints, that slow down things, so FVM removes them to prioritize the preload headers, necessary for the critical css and js files (render blocking).

For CSS you can choose what to async, and there is no link preload.
For JS only what you put on the render blocking section will have a link preload.
And you can disable both preloads, using the Disable CSS Link Preload, or Disable JS Link Preload.
Just tested this and working.

Combining CSS/JS is no longer recommended if you are on a modern hosting or use a CDN, however you can still do it if there are no conflicts (merging somethings breaks scripts).

If you are seeing “popper.min.js, bootstrap.min.js and core.min.js” then probably, you haven’t configured the plugin Render Blocking JS files, Defer JS Files, Defer Inline JavaScript, Delay third party scripts until user interaction, or perhaps you have disabled minification.

CSS is processed automatically and you can then ignore or async what you want.
JS is manual, so you need to specify what you want to render block, defer or delay.

On the settings tab there are suggested defaults, though each site needs it’s own settings, so you need to try and see what works for you.

This doesn’t happen on a default WP 5.9 / PHP 8 setup, at least not on my servers, but I just added some changes to try and avoid this. Please update. Thanks

It works with WP 5.9 and PHP 8. Not being officially tested, doesn’t mean incompatible. Thanks

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.

yes, it will be on the next update today. Thanks

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

Not tested, simply means that there hasn’t been an update but It’s fully compatible with WP 5.9 and PHP 8. Thanks

Thanks, this will be fixed on the next update.

This is fixed on the next update. Thanks

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.

Sometimes when the cache grows too big, or when the hosting has a slow disk, some files may be left behind. You can either manually purge the directory (after cache purging, it will regenerate again), or enable the instant purge option https://i.imgur.com/gGi0tNi.png if your hosting is supported.

@jdembowski thanks, but I was talking specifically about the free elementor version. That is the one that breaks things after the update. I had to downgrade it back to 3.4.8 anyway, as it caused other issues.

Elementor Pro while also there, doesn’t affect the issue… but I will contact elementor support directly.

That error is unrelated to PHP, it’s a JavaScript error.

Please check if disabling FVM and clearing your cache makes.it disappear.

If it does, you need to exclude that file from minification. The script is not compatible with the minification library used on FVM.