clwill

I was chastised for posting on that thread. So I came here.

Yes, I have cleared my cache. No I’m not running any plugins. No, it’s not a mod_security issue (my host tells me they’re not running it, and I’m getting a 404 not a 406). Yes, a health-check is clean. In short, I’ve tried everything there.

Same problem here. Brand new empty WP site, latest WP, no plugins, running 2017 theme. Saving customizations gives this same error. I have a dozen other WP sites running latest WP, no problem. Host is ASmallOrange, they couldn’t be less helpful if they tried.

Any ideas?

I’ll run a phpinfo() query to see where I am on those, but wouldn’t that prevent it from running on a “run now” or at least every time it runs unattended? My problem is that they’re erratic — running sometimes not others. For example, several of the dailies are now running successfully, but they haven’t run at other times.

Thx,
Chris

The host is ASmallOrange. I don’t have any “resource limits” that I know of. Disk space? Not an issue, at less than 3% the quota. What other limits would you suggest I look at?

I’ve checked two of the sites, both dailies ran last night. But it appears to be flaky.

Is there any kind of logging mode I can turn on? Some kind of error handling to enable?

I’ve just checked, and now none of the backups are running. Daily, weekly, nothing. And past backups have disappeared. Just updated to the very latest, reset all the schedules. We’ll see, but this is getting scary and frustrating.

This is silly. Now they just worked this week… Haven’t worked forever. Maybe the recent updates, and maybe doing “run now” on them all worked? Dunno.

To answer your questions: yes, same server. Five are the same size — pretty small, two much larger. They all run badbehavior and jetpack, as far as “security” plugins, other plugins vary mostly for looks and that sort of thing. They all “run now” fine, they all run their daily runs fine, it was just “on schedule” “complete weekly” runs that didn’t work.

However, as I noted, this week they all ran (for the first time) by themselves. Spooky, must have known I was talking about them :). I’ll let you know if they don’t run next week.

Thx for the response.

Thank you, wasn’t aware of development mode.
And thank you for getting the stats back.

Now, if you can just fix the “mixup” notice so that it actually does something ??

Chris

To further clarify, we had aaca.clwill.com as a test/staging site. We went to make it live and moved to aacasouthflorida.club. Since then I’ve been getting these announcements.

I have tried, on both the staging site and the live site to choose either the “ignore the difference” link or the “that used to be” link (as appropriate) and neither link seemed to do anything — either in the fact that nothing seemed to happen when I clicked on them, or in dismissing the notice.

The only thing that worked was the disconnect/reconnect, and loss of the stats.

Thx for any help you can provide.

Thank you! It’s aacasouthflorida.club. Would love to have them back!

Having the same issue. Clicking on the options did nothing. But reconnecting, and losing all my history fixed it. Bummer.

AND… nevermind. I see that the user has declared those links with the WP link tool (in the editor) specifically asking that the be opened in an external tab. Will have them fix those.

Sorry for the false alarm.

Sure, every link on this page: https://familylemonadestand.com/productivity/

Thanks. The site is https://familylemonadestand.com, and it’s running WP 4.1 with customizr 3.2.17.

I have this same issue. No amount of fiddling with the “open external links in new tab” fixes this. Turned it on, saved, turned it off, saved. Cleared caches in the browser (chrome), restarted browser, still there. The “target=_blank” is still on every external link. Tried in Safari, which I haven’t used in months. Still there.

Something’s definitely broken here.

I did posted different info in two threads. I posted once in here to note that this is still an issue. And when pointed to the “how to report a bug in BB” thread, I posted in there to note that I couldn’t report a bug as described.