Hi,
FVM is a speed optimization plugin, merging the css and js files together. It is not aware of when you save stuff on elementor, or when you are doing development and editing css and js files via sftp or via some other methods.
It’s standard procedure to disable minification and any other cache plugins, including cloudflare and cdn services, while editing css/js files, or making design changes.
For small changes in design and content, you don’t need to disable the plugin or server cache, but you still need to purge it after you are done with all the changes, manually. Even if some plugins do this automatically, you should still do it manually as you can never be 100% sure that they actually purged the cache all the time.
Cache and minification is to be deployed on the final product, not during development.
New content doesn’t usually apply to this, as it’s also new to the cache and minification plugins.
It’s also not all the time that you need to purge caches when using elementor. It depends on what you are doing. If you are editing css and js files, then you must always purge the cache on FVM for it to restart the optimization again with your new changes.
Also if you use any sort of cache, either a plugin, on the server side, or a cdn, that also needs to be purged every single time you save different css, js or new design in a page. That’s how the workflow works for design and development, for sites in production.
In staging, you would be running a copy of your site without any cache and without any optimizations. Optimization, is only after you are done and are going to deploy the code live.
I’ll take a look at elementor sometime later and see if I can set an automatic trigger, but in most cases, you should still do it manually (there is a cache purge button for that).
