well, as per the AO FAQ there is no auto-delete in AO and I strongly advise against it because a fast growing cache is an indication of more important issues. instead it is better to reconfigure AO (don’t aggregate inline JS to start with) to make sure the cache does not “explode”.
that being said, if you insist, the FAQ does have links to 3rd party solutions to auto-purge the AO cache 🙂
enjoy your friday!
frank
What can be reason of fast growning cache?
http://piwnypamietnik.pl/
most of the times this is due to inline JS being aggregated that has parameters that change (based on time or user or page). sometimes inline CSS, sometimes CSS stored in wp-content/cache or wp-content/uploads (which are excluded by default).
So what can I do with it?
well, unticking “also aggregate inline JS”, optionally also unticking “aggregate inline CSS” and double-checking if wp-content/cache
or wp-content/uploads
are in the CSS optimization exclusion list?
lots of info in the AO FAQ too, by the way 🙂