• I am using auto optimize 2.2.2 and the cache file is growing very very fast. I have gone trough 5/6 pages in support forum and you have suggested to disable “aggregate in-line JS” and optionally “aggregate in-line CSS”, in my case both are disabled how I can deal with it? But more important part is why it is happening?

Viewing 9 replies - 1 through 9 (of 9 total)
  • Thread Starter Prafulla Kumar Sahu

    (@prafulla)

    I got this yourr blog post got some idea, but not able to solve it and also I would like to know more about it.

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    it is happening because the JS or CSS (see how many files you have in wp-content/cache/autoptimize/js vs wp-content/cache/autoptimize/css to see which one is causeing this) between two pages is different, in which case there no cached version and a new cache-file is created.

    if both aggregate inline css/ js are already de-activated, the problem could be due to a plugin (or your theme) writing their own dynamic code into static (cached) files, typically in wp-content/cache (like AO does) or wp-content/uploads. have a look at your unoptimized HTML source (add ?ao_noptimize=1 to your URL to disable AO, allowing you to see the page without autoptimize), try to find such URL’s and exclude them from Autopimization.

    hope this helps,
    frank

    Thread Starter Prafulla Kumar Sahu

    (@prafulla)

    Hi Frank, thank you for your kind reply again. I will follow your suggestion and report to you. In this time, I have gone through several pages of your blog and got about these plugins, I would like to know if I should move to any of them or there is any method to allow wp super cache to clear auto optimize cache in some interval keeping its own cache file safe. Will it be harmful, is it possible?

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    No, you can use WP Super Cache (I do too on some of my sites), but no page caching plugin will clean Autoptimize’s cache automatically I’m afraid. There’s a plugin that claims to do that, but I haven’t tried it myself.

    frank

    Thread Starter Prafulla Kumar Sahu

    (@prafulla)

    Thank you Frank, I gone through you blog for around 5/6 hrs and loved it. I would also like to know is there any way to separate cache generated by auto optimize from wp super cache? So that cache file related to only auto optimize will be removed and rest will remain as usual, is it possible? Will it harmful?

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    is there any way to separate cache generated by auto optimize from wp super cache? So that cache file related to only auto optimize will be removed and rest will remain as usual, is it possible?

    no, that’s not possible, as the cached pages (by WPSC) will have references (links) to autoptimized CSS/JS that would have been deleted. If you want to be able to delete the autoptimized cache (automatically), you’ll have to empty your page cache as well.

    Thread Starter Prafulla Kumar Sahu

    (@prafulla)

    Thank you so much Frank.

    Would it work if I wrote a cron job that automatically deletes the files in the cache/css and cache/js directories that are a day old? I guess I’ll find out for myself…

    Plugin Author Frank Goossens

    (@futtta)

    Would it work if I wrote a cron job that automatically deletes the files in the cache/css and cache/js directories that are a day old?

    Only if you make sure there is no HTML in a page cache that refers to the CSS/ JS you’re about to automatically delete. Have a look at the FAQ for more info about cache size and how to manage it.

Viewing 9 replies - 1 through 9 (of 9 total)

The topic ‘Why auto optimize creates so large cache file?’ is closed to new replies.