Why would you want to do that?
The cache files generated by FVM are for CSS or JS files only, and these will probably never change. (If you changed it manually, then you can press the purge cache button on the plugin status page).
It doesn’t cache your pages html.
If you delete the JS or CSS cache files, while you use a cache plugin, your html will still reference your (now gone) css and js files… thus breaking your design.
If you use a cache plugin such as W3 Total Cache, you can set the amount of time
we are having the problem, that the cache runs full and then parts of the webshop dont work anymore. We dont know why this is but we the purge button helps solving it. So the idea war that the purge happens every day so the cache gets deleted more often.
You mean you’re running out of disk space because there are too many files generated by fvm?
In that case, you probably have a dynamic css file, which changes name every pageview.
You need to see the name of the file and add it to the ignore list.
If you cache that file, it will always generate a new cache file because the name changes every time.
no its not the physical space. its about the cache
But the cached files are on the disk, under wp-content/uploads/fvm.
Are you talking about the transients database cache?
For either reason, what I said earlier about using the ignore list is the same.
You have to see which one and exclude that dynamic css file via the ignore list.
You can purge the cache once, refresh the homepage and see the “view log” option.
There should be a file with a ?somenumbers there.
What’s your site url?
ok, sorry for missunderstanding.
its http://www.tapemuzik.de
Yes, you’re using the Divi theme, and it probably has a dynamic css file, which you need to exclude via the ignore list.
How are you checking that the cache is full, and how do you know it’s this plugin?
Clearing the cache on FVM also deletes the cache on your cache plugin (usually), in case you’re using one.
Either way, look at the logs and exclude that file with a question mark via the ignore list. If there is none, then it’s probably not this plugin but rather some other cache plugin you may be using.
