Paddy Landau

@elenachavdarova — Elena, I’ve made a note to review the plugin, which I’ll do after I’ve used it for a week or two.

That’s great, Elena, thank you!

Thank you, Elena.

Thanks for the response, Michelle. I suspected as much.

The browser saves the cookie just fine; it works correctly when viewing the site and in the back-end. It’s only when editing pages or posts on this specific theme, as it has a particular quirk due to the nature of its functionality. (Other themes don’t have this problem.)

I’ll put up with the minor inconvenience, because otherwise I risk forgetting to re-enable the banner when going live.

Thank you for your reply, @madhattersez

Since you posted, I haven’t done anything (apart from automatic updates being allowed to run), and now…

• Jetpack no longer shows a pending update on this site.
• On the other hand, Jetpack shows pending updates for four of my other sites!

Like my first site, the other four sites are all up to date and don’t use caching.

I am guessing that this is a temporary thing, so I’ll wait a couple of days to see if the other sites clear by themselves as the first one did.

Thanks for your time.

I have no caching plugins. As far as I know, my host (GoDaddy) doesn’t provide caching.

The only caching is Jetpack’s site accelerator.

I deactivated all plugins except Jetpack, but that didn’t help.

I deactivated Jetpack and reactivated it, and again that didn’t help.

I disabled Jetpack’s site accelerator, and again that didn’t help.

If I uninstall and reinstall Jetpack, will it remember my settings?
If not, is there a way to export the settings and to import them after reinstalling?

Thank you

Thank you for your reply, Animesh.

Jetpack was updated early this morning (I have auto-updates enabled on all of my themes and plugins).

I have Jetpack version 9.8.1.

It’s OK, I figured it out.

I installed Cron Jobs, and that let me delete the job.

Thank you, Stef, the link was perfect.

I have added this to my .htaccess file along with a custom error document for 403 errors, and so far it seems to be working perfectly.

Jetpack hasn’t complained; wp cron works; I can access the site from my specified IP addresses; and everyone else gets the custom error.

Ron, I didn’t manage to resolve the issue. I check the website as part of my daily tasks, and manually run updates when they’re required.

Interestingly, it’s a bit more complicated. When I go to various websites in the Update tab in the backend, I see the following.

On the website for which I created this thread, it reads:

This site will not receive automatic updates for new versions of WordPress.

Another website reads:

This site is automatically kept up to date with each new version of WordPress. Switch to automatic updates for maintenance and security releases only.

The last line has a link to /wp-admin/update-core.php?action=core-major-auto-updates-settings&value=disable&_wpnonce=268f5f13fd

All other websites merely say:

This site is automatically kept up to date with each new version of WordPress.

My guess — it’s only a guess, though — is that somewhere along the line, a plugin or theme has set some WordPress flag.

I keep all sites fully up to date, so they’re currently all running WordPress 5.6.2 with the latest available plugins, themes and translations.

• This reply was modified 3 years, 8 months ago by Paddy Landau.

Thank you, Gregory. The funny thing was that I had tried that, but it didn’t work. However, more than 60 minutes has passed, so I can log in again.

Thank you. I think it must be something else causing a problem, though I can’t imagine what, because this is what happens:

1. I go to /wp-login.php
2. I log in
3. After login, I’m redirected to the home page instead of the Dashboard
4. When I try to go to /wp-admin, I get the message, “Sorry, you are not allowed to access this page.”

I shall re-copy the entire site, but with wp-cerber disabled before copying.

Thanks again for your help.

No, I absolutely deleted the plugin folder. To confirm, the folder was:

/wp-content/plugins/wp-cerber

I deleted the entire folder. I have triple-checked now, and it’s definitely absent.

Thanks, but unfortunately that didn’t work. I can now enter my login details, but I get the message, “Sorry, you are not allowed to access this page.”

I’m going to have to take a different approach: I’ll disable wp-cerber on the source website, copy it to the target website, and then re-enable wp-cerber on the source website.

I don’t want to disable wp-cerber for obvious reasons, but I don’t see an alternative. Unless you can think of one?

Thank you, Olga.

As it’s a new installation, I might just reinstall from scratch.