Hi –
Please send along a screen shot of the message you’re seeing. Also, let me know which site you’re working on. Then we can take a proper look at what’s going on. Thanks 🙂
That’s an interesting bug!
Manage is now a required part of Jetpack, but previously it could be switched off. I think this is some sort of an edge-case collision in sites that previously had it off.
Please try deleting Jetpack specifically from the Plugins section of your blog’s Dashboard: https://jetpack.com/support/reconnecting-reinstalling-jetpack/#reinstalling-jetpack
This will clear out Jetpack’s settings, and it should work properly after a reinstall.
Alternatively, since the point of the re-install is just to get Manage working anyway, try the “Activate Jetpack Manage” button.
Meanwhile, I have filed a bug report on this: https://github.com/Automattic/jetpack/issues/12232
Hi there – I will give that a try but a little confused.
You say it’s a requirement now, but you can still have it off? …or is it a requirement to be able to use certain features?
Also, if I Activate it as you suggested, then how do I turn it off if you can’t selectively do that anymore?
I just don’t think we have a need for it as it seems it’s only useful for running multiple sites in the one JetPack account?
Sorry if I was a bit abrupt in my first post.
Thanks 🙂
You say it’s a requirement now, but you can still have it off?
It’s on by default for new installations, and there’s no way to turn it off anymore.
It allows you to manage your site via WordPress.com, and now some of Jetpack’s settings can only be controlled via WordPress.com.
Ok thanks.
Enabling it has gotten rid of that message; another reason I wasn’t 100% sure on enabling it was I didn’t want to slow the site down as I assume being connected to JetPack management does communicating back and forth.
