cwdv

Okay thanks,
I plan on starting some new projects utilizing Twenty Seventeen. How different will the new theme be from Twenty Seventeen. Will it be radically redesigned for Gutenberg/WP 5.0?
Thanks again for your help,
Clint

Okay Thanks, Hopefully that can get incorporated into phase 2.

I was also wondering, when WP 5.0/Gutenberg is released will it include a new theme?

Thanks again,
Clint

@bkproductions, Sounds like we are on the same page. Surprised this hasn’t already been implemented. In my option it would be a nice addition.

Anyone?

Done, sent via email Thanks….

Hello,
I just checked again right now, and I noticed the cache preload is working, but I also noticed that it is caching the items I excluded that utilize the “Start With:” Rule.

Thanks again,
Clint

I am having the same problem. I am using a premium theme with no version listed in the WordPress theme repository. Is there anyway for you to troubleshoot this?

Hello,
I just sent my site URL to the link you posted.
Thanks,
Clint

I confirmed that the “Restart After Completed option was NOT selected and then I selected Submit.

I installed the recommended plugin Cron Manager, and the “WP Fastest Cache Preload” cron disappears after the Preload is complete, but it reappears after the “Cache Timeout” option runs and it starts preloading again. It continues to cache 6 each time, which is what I have set for “Pages Per Minute”.

I find it very odd that it works for you. I apologize if I am overlooking something, but I don’t know what it would be at this point. My site is running HTTPS, not sure if that makes a difference?

I think I would actually prefer that the preload continues to run, so I will likely select that option in the future.

Just checked my logs, and yes I still see that user agent.

Just checked, it says “Completed”.

I checked by matching the cache timestamps in Cpanel with my Server logs and found the user agent referenced above.

I hope I am not missing anything, but I double checked the Preload options by unselecting and reselecting Preload to bring up the dialog box and the “Restart After Completed” option is NOT selected

The Preload option “Restart After Completed” is NOT selected, and after the Cache Timeout expires, new caches are being created by the Preload. I checked my logs for the new cache timestamps and they show the user agent is “WP Fastest Cache Preload Bot”.

My understanding from our discussion, is that no new caches from the Preload would be created after that. New caches would only be created after someone visits each site page.

Thanks again

Okay, if we want the preload feature to function like it did before this last update, do we need to select the “Restart Preload After Completed”?

If we don’t select it, will it preload one time only?

In your previous response you state:
Based on the info you provided, this does not mean your site down, it means your site is not responding well enough

When you reference “not responding well enough”, does that essentially mean a connection was established with the server and the initial head request was received by the server, but jetpack monitor had to wait to long for a response from the server?

I was also wondering, do the times in jetpack monitor emails represent the timezone setup in WordPress, or on my server?

In the future, is there any chance Jetpack Monitor could include the actual HTTP response code in the notification emails?

Thanks again for your help,
Clint

• This reply was modified 7 years, 1 month ago by cwdv.

Okay,
I see that it is already added to the plugins .htaccess additons. I was just wondering if having it in there more than once was a problem.