Preload has been restarted (no email notification marked)

Hi @sapphire,

Since this is happening only on a specific site, can you please share the URL so we can take a look? If you want to keep it private, you can share it using this contact form.

Thank you!

I’m confused. That’s a Jetpack support page, and I don’t see a contact form, just FAQs and a chatbot. I tried to use the chatbot but it just said it doesn’t have any “quick answers” for me and to rephrase. I do need to keep the site private.

+1
Since the last update all updated sites throw the same error here, too:

Preload wurde neu gestartet. https://domainname.de/wp-admin/options-general.php?page=wpsupercache

The last website shot new messages all few seconds and so I had my inbox full of such mails within minutes – not funny!

Especially as reporting via mail was turned OFF.

1st I disabled preloading but the mails didn’t stop. Then I deleted all WP caches but that didn’t help either. Finally I cleared the serverside caches (OPcache & APCu) and then it stopped.

So @alinclamba, I can tell you: it’t NOT “a specific site” ??
I’m using WP Super Cache from day one and never had that. So I strongly assume it’s some kind of newly introduced bug.

And as we use WPSC on ALL our sites, I’ll get into real trouble with that if it won’t be fixed immediately…

Same issue here! After the update, even with “No Email” set, the email messages are now suddenly being sent. My guess is something in the update ignores this setting now.

Is the system preloading pages? Do you see lots of cached pages, despite the emails you’re getting?

If you’re able to, you can disable the email notifications in the code. Navigate to wp-content/plugins/wp-super-cache/ and edit the file wp-cache.php

Go to line 3400. It looks like this:

wp_mail( get_option( 'admin_email' ), sprintf( __( '[%s] Preload may have stalled.', 'wp-super-cache' ), get_bloginfo( 'url' ) ), sprintf( __(   "Preload has been restarted.\n%s", 'wp-super-cache' ), admin_url( "options-general.php?page=wpsupercache" ) ) );

Put // at the start of that line, save the file, and it will disable the emails.

The system restarts the preload process, but there must be something not quite right on your sites that causes this problem. We’ll have to look into it.

• This reply was modified 1 year, 1 month ago by Donncha O Caoimh (a11n).

“there must be something not quite right on your sites that causes this problem.”
^^Since we use WP Super Cache for years now on all our sites and never ever had such an issue as well as we didn’t modify anything that could have caused that AND since the affected people here surely have different hosts there can’t have gone something wrong at the same time with all of them, I don’t think, the problem is on our sides…

And the main problem aren’t the annoying mail, but the preloading trouble – and in the worst cases broken websites because of this (happened to some of our sites and was fixed directly by deactivating WP Super Cache. And all our sites have separate Hostings, not one common shared hosting. Additionally the problem also affects customer sites we don’t host as resellers, So the problem occurs with our premium hoster, their hosters and all the hosters of the people who also wrote in this and common threads at the same time…

Please take responsibility instead of pushing it away and work towards solving the problem. That would be really great.

• This reply was modified 1 year, 1 month ago by yellowfellow333.

@yellowfellow333 What I meant, is that the plugin saved data related to the preload incorrectly on your sites. I’m not saying you changed anything to make it break, sorry about that. We’ll get this fixed.

How did the sites break if it was only preloading that was broken? Were there any errors showing? Or do you mean, without caching they broke?

Most sites worked. But in rare cases only fractions were shown like a giant hamburger Icon, another hugely scaled graphical element and unformatted text on a blank white page. Looked like a half-rendered/half-cached output. Couldn’t fix that by clearing the cache, only deactivating helped for the moment.

Must say that I didn’t inspect that too intensive because I’m there that my client’s sites keep staying online, not offline (was in a hurry and needed quick solutions). What I didn’t test there was clearing the ACPU/object cache on hoster side (only ‘clear cache’ in WP and browsers; tested with Firefox and Edge).

@yellowfellow333 Sorry for the late reply. I haven’t seen that happen very often. Next time you do see it, check the cached pages on the server. See if the files are complete, or somehow corrupted. Did you see these corrupted pages when you visited the sites, or is it user reports from others? And the same corruption on the one page was seen in multiple browsers, like you said, tested with Firefox and Edge?

@donncha
I saw corrupted pages – not formatted via CSS, only plain text on white and all graphics full resolution 1:1. But the main problem were the preloading error messages – and with them allegedly also real preloading errors which never ever occured on a single site before and now suddently affected all sites. I’ve preloading still off on all of them; did you already find the problem?

@yellowfellow333 I wasn’t able to find a problem with preloading, but I know there is an issue, from the complaints in this thread.

Preload uses the standard wp_remote_get() to fetch the web pages to preload. And it does it fairly slowly, with a 1 second pause every time it fetches a page. It’s really surprising to me that it would cause pages to be corrupted. If anything, preload was more intensive before. It’s slower now.

If you see it happening again, can you take a look at the cached files for the corrupted pages? Are they saved corrupted? Is there a pattern to where the corrupted pages are damaged? This plugin does nothing to minifiy or adjust CSS or JavaScript files. Is there another plugin installed on those sites that does that job? Maybe this plugin depends on the user agent to decide on what minification or other optimization to do?

I’m hoping to find time over the next week to work on the preload code, but you can comment out the wp_mail() to stop those emails in the meantime.