How to Use FTP to Deactivate a Plugin That’s Breaking Your WordPress Site
WordPress plugins can cause all kinds of errors: 500 internal server errors, PHP parse errors (also called syntax errors), errors that simply whitescreen your entire site, and more.
What’s worse, it’s often the case that a WordPress plugin that’s causing a PHP error will take down not only your site’s frontend, but the backend—
wp-admin—as well. That means it’s impossible to deactivate the plugin (turn it off) with only WordPress admin access, resulting in a permanently broken site.
There is a fix for this problem, but it requires FTP access (or SSH access if you’re fancy like that). This video shows you how to use FTP to deactivate a plugin that’s erroring and breaking your WordPress site:
Here’s a text summary:
How to Deactivate a Plugin That’s Breaking Your WordPress Site with a Fatal Error
- Establish an FTP connection to the site. If you don’t know how to do this, read more about FTP. You’ll need hosting access to the site to be able to do this part.
- Navigate to the plugins folder of the site. By default this is
- Find the folder name of the plugin that’s breaking your site.
- Rename that folder. In the video example, we rename the folder
- Reload the site and both the front-end and
wp-adminwill be back up and working.
Bonus tip: If you don’t know which plugin is breaking your site, you can use FTP to deactivate all plugins at once, by simply renaming the plugins folder itself—for example, to
Thanks for reading!