Cache generation is triggered automatically when somebody hits an uncached page provided your entire cache size is below the limit. The trigger itself is hooked to the template’s footer. So cache-folder-size based generation is not cron-dependent.
Though I do agree: it might still be a good idea to add such button in the next release.
Thanks for suggesting.
Thanks, that’s good to know. I think I was probably being too impatient in trying to load up pages before they were cached. Next time I update, I’ll empty my cache, hit the homepage and leave it a while longer – maybe I’ll have to go away form the Mac & have a coffee before trying to load the other pages.
Hi Denis,
I have been looking for a plugin that coud facilitate the cache generation without waiting for my thousands blog pages to be visited in order for it to generate its cache. I do believe that your plugin is what i was really looking for. I have installed it and setup the intervel to 5 seconds and I clicked generate cache button. After nearly an hour I can still see the cache generation in progress and I was thinking that it was normal because of the size of my website. Then I checked my cache folder using my ftp client, but I was surprised that there was no newly cached pages or posts. And when I checked my errors log file there was no errors.
Is that normal? Does the plugin need to generate all pages in order for it to write them at once in the cache folder? or does it write every single file individually?
Thanks a lot for the great plugin and mostly for your time.
