Locked out of WordPress due to Jetpack issue

Hi @modflowers, the “headers already sent” warnings are usually caused by output being sent to the browser before the system sends HTTP headers. In your case, they seem related to the deprecation notice.

As the deprecation notice says, Jetpack no longer supports Custom CSS. It’s probably the theme of your website that was using this feature. If you can’t disable Jetpack and other plugins from your hosting control panel, you can do it using FTP:

1. Connect to your website using an FTP client.
2. Navigate to the?/wp-content/plugins/?directory.
3. Find the?jetpack?folder and rename it to something like?jetpack_disable. This will deactivate the plugin. Repeat this process for any other plugin that you want to deactivate.

After doing this, try to access your WordPress dashboard. If the problem is resolved, I recommend updating the Jetpack plugin to the latest version.

If you’re not comfortable using FTP or the issue persists, you may want to contact your hosting support team for assistance, as they can help you disable the plugin directly on the server.

Thanks for your response. I contacted my host and they were able to help me to disable Jetpack, after which I was able to log in and access my WordPress dashboard.
Which is good, but I still don’t know what I need to do to fix the site going forward, as it was built using a theme that was modified with custom CSS to look the way I wanted. The site still looks the same, but is this just because I’m viewing a cached version? I haven’t yet tried clearing the cache to see if it then looks different. If Jetpack no longer supports custom CSS, then presumably my site is going to just break again if I reactivate Jetpack. What happens if I just don’t reactivate Jetpack? Its always been there on my site, but a lot of the functionality that it had when I first installed it isn’t there any more. Do I actually need it?
I can access my dashboard, but basically have no idea what I need to do now!

Hi there,

If Jetpack no longer supports custom CSS, then presumably my site is going to just break again if I reactivate Jetpack.?

Sorry for the confusion here! What we meant is that Jetpack no longer supports its own Custom CSS feature, because Custom CSS is now included as part of the WordPress Core software.

To continue using Jetpack on your site, please reconnect it, and then go to Jetpack → Settings → Writing?in your site’s dashboard. Scroll down to the?Theme Enhancements?section and toggle off the?Enhance CSS customization panel?option.

That should allow you to continue using Jetpack, without any errors appearing on your site.

Its always been there on my site, but a lot of the functionality that it had when I first installed it isn’t there any more. Do I actually need it?

This depends! The free version of Jetpack can do a lot of things in terms of performance, growth, and security for your site, including:

• Brute Force Protection again malicious login attempts
• Content Delivery Network to speed up loading times
• Activity Log of the most recent events on your site

a lot of the functionality that it had when I first installed it isn’t there any more.

Can you be more specific about what functionality you were using before?

Hey @modflowers,

Do you have updates about that? 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!

Hi @stef (a11n), I followed Emily A’s advice above, which enabled me to reactivate Jetpack.
In response to her query, one thing I remember that I used to use Jetpack for was to provide a mobile-friendly version of my site (as my theme doesn’t come with this option) but Jetpack no longer provides this.
My site still works, so I guess that means that my original question has been resolved.
Many thanks!