Hi there, @wombatssa,
The 404 errors you’re encountering might be due to a plugin or theme conflict. Please try troubleshooting for conflicts by deactivating all plugins except Jetpack and switching to a default theme like Twenty Twenty-One. Then, reactivate each plugin one by one to identify the source of the issue.
Let me know what you find out, and we’ll take it from there if necessary.
Hello @wombatssa,
Do you have updates about that, do you still need help? We usually close inactive threads after one week of no movement, but we want to make sure we’re all set before marking it as solved. Thanks!
Hello Stef,
That suggestion seems sensible, but I am concerned it would wreck the site while the plugins are all inactivated and testing is being done.
Some plugins are essential to the appearance and security and member access to the site.
So I am not willing to do that.
If there is no other way to check, I will wait until our replacement site (under way) is ready to go live and see how that goes.
Thanks,
Merv
Hi there,
If you’re concerned about deactivating plugins on your live site, consider setting up a staging environment. This allows you to safely test for conflicts without affecting your live site. Many hosting providers offer staging sites, or you can use a plugin like WP Staging to create one.
On a side note, I can see an issue with the connection between your site and Jetpack. This could be related to your problem. We require a user-authenticated connection to WordPress.com. Jetpack is a plugin that allows you to use features we developed on WordPress.com on your self-hosted website through the Jetpack plugin. Since these features were built for WordPress.com sites, we need to connect your site via the Jetpack plugin to a WordPress.com account. You can find more details about this here:
https://jetpack.com/support/why-the-wordpress-com-connection-is-important-for-jetpack/
Please follow these steps to connect:
- Go to the Jetpack menu in your WP Admin dashboard
- Access your Jetpack → My Jetpack
- Scroll down to find the Connection area
- Click Connect your WordPress.com account to connect Jetpack to your WordPress.com account
Let us know when you have done this, and we can take another look at your Jetpack connection.
It’s possible that initial issue get fixed by this.
Cheers,
Hey there, @wombatssa,
Touching base to hear from you, whether our last suggestion worked for you, or if you still need help. As mentioned earlier, we usually close inactive threads after one week of no movement, but we want to make sure we’re all set before marking it as solved. Thanks!
I set up a WordPress.com account for Wombatssa.
Looking at the “My-jetpack/Connection” page element I see It already sems to be “connected” ?
Not sure what/who to … I have a personal WordPress account I used to create a Gravatar, but it’s not connected to that.
Please advise next steps.
Thanks,
Hi @wombatssa –
Right now, your site is connected to WordPress.com, but via a “site-only” connection instead of a user account. We have an explanation of the differences here: Why the WordPress.com connection is important for Jetpack.
For now, I think you can ignore that. The more important thing is to determine whether the issue goes away when you have all plugins other than Jetpack and WP Super Cache disabled. Please enable debugging in WP Super Cache and disable the plugins. If it no longer happens, the issue is one of your plugins. You would then want to add one at a time, testing along the way, until you find the one that causes the issue.
Let us know how it goes.
Hi there, @wombatssa,
Do you have more updates about that, or do you still need help? As mentioned, we close inactive threads after one week, but we want to make sure we’re all set before marking it as solved. Thanks!
