Thread Starter
Jim
(@jwmc)
That doesn’t seem to help. I modified the cron job (every 15 minutes, the fastest allowed) so I could see the page response and a log:
wget -O ${HOME}/logs/preload-page.html -o ${HOME}/logs/preload-log.txt "https://forestpathology.org?action=wpfastestcache&type=preload"
I cleared the cache in WPFC settings and watched the cache in FTP. It’s building slowly still like before, most popular pages first. The response page mentions 6 forum pages, but there are 50 or more regular pages still not cached.
OK https://forestpathology.org/fora/forum/general-forest-pathology/ (desktop)
OK https://forestpathology.org/fora/forum/wilts/ (desktop)
OK https://forestpathology.org/fora/forum/parasitic-plants/other-parasitic-plants/ (desktop)
OK https://forestpathology.org/fora/forum/parasitic-plants/true-mistletoes/ (desktop)
OK https://forestpathology.org/fora/forum/parasitic-plants/dwarf-mistletoes/ (desktop)
OK https://forestpathology.org/fora/forum/stem-decays/ (desktop)
6 page have been cached
homepage: 1/1
customposttypes: 23/40
post: 0/1
page: 0/68
you can change the 15 minutes as 3 minutes.
Thread Starter
Jim
(@jwmc)
15 minutes is the most frequent the hosting will allow me to do a cron job. But what difference does it make? When it starts a preload, shouldn’t it go on and cache all pages on the site until they are all cached?
Thread Starter
Jim
(@jwmc)
Well . . . it doesn’t, on my site.
can you be sure that WP_CRON works on your site please? can you add a scheduled post please?
Thread Starter
Jim
(@jwmc)
I have WP_CRON disabled in wp-config.php, then call wp-cron.php with a system cron job every half hour. I did schedule a post as you asked, and it was indeed posted on the half hour when the cron job ran.
I think I’m beginning to understand how WPFC works with preloading. I edited the cron job to save the response html file with a time stamp, so I can see them all and see what it is doing each time.
When the Preload dialog is set to “6 pages per minute”, that is not what happens. The preload just tries to cache 6 pages, then it stops dead, until it is called again. If some of those pages are excluded, doesn’t matter, they count toward the 6.
I don’t understand why it works like this, certainly not from the documentation. When you preload, why not go through every post type that is checked, and if the post is not cached, cache it. Don’t just do 6 and stop. Keep going until the job is done.
-
This reply was modified 5 years, 7 months ago by
Jim.
Thread Starter
Jim
(@jwmc)
Also, when running it as a cron job, it just keeps replacing already-made cache files that are just fine. This seems to waste resources.