hi mrmcon;
that’s bad, I would be very bummed out myself!
some clarifications are warranted here;
the warning mail is sent if the cache is bigger then half a gigabyte. what happens when the cache is “full” (which is all disk-space of your account being used I guess), is not something autoptimize controls I’m afraid.
if the problem indeed was with cache size, removing the cache should have fixed the issue, if you needed a restore to get things workign again, there very likely was something else going on …
as per the FAQ, don’t aggregate inline JS and there should be no cache problem.
hope this clarifies,
frank
Thread Starter
MRMCON
(@mrmcon)
Hi Frank
Thank you for the response.
I have removed the “dont aggregate inline JS”, will keep an eye on it.Overnight seems good.Only cached 6mb.
Perhaps the the plugin could warn users a bit sooner
Regards
Mark
well, half a Gig is soonish, taking into account most hosting plans come with a substantial amount of disk space no? 🙂
keep me posted on cache size, I’ll be happy to help you troubleshoot/ finetune further!
frank
Thread Starter
MRMCON
(@mrmcon)
Hi Frank
Just an update, i have followed as above(no other changes) and all is ok now.The cache sizes remain small.
Thanks
Mark
great! guess that warrants a change in rating, no? 🙂
Thread Starter
MRMCON
(@mrmcon)
Hi Frank
New rating 4/5 stars (did try change).Plugin works well, for new users (like myself) it is advisable to be more thorough on the guides and FAQ before activating.
Thanks to Frank for the quick support.
Mark
New rating 4/5 stars (did try change).
I think you have to go here and click on the 4 stars @mrmcon
for new users (like myself) it is advisable to be more thorough on the guides and FAQ before activating.
In the next version of AO there will be an explicit warning next to the “also aggregate inline JS”-option:
Let Autoptimize also extract JS from the HTML. Warning: this can make Autoptimize’s cache size grow quickly, so only enable this if you know what you’re doing.
frank
