My WooCommerce Site Crashed After a New Plugin
Why This Works
WordPress checks for each active plugin's file at its expected path on every page load, and if that path no longer exists (because the folder was renamed or removed), WordPress simply treats the plugin as deactivated rather than throwing an error about it. This makes folder renaming via FTP or a hosting file manager a reliable way to disable a broken plugin even when the WordPress admin itself is completely inaccessible.
Step by Step
- Access the site's files via FTP, SFTP, or the hosting control panel's file manager — this doesn't require WordPress admin access at all, which is exactly why it works when the dashboard is broken.
- Navigate to
wp-content/plugins/and locate the folder for the plugin just installed. - Rename that specific folder (appending anything, like "-off" or "-disabled", works) rather than deleting it, preserving the plugin's files in case you want to investigate further or reinstall it later.
- Reload the site to confirm it's now accessible again with that plugin deactivated.
After Restoring Access
- Enable debug logging and check what error the plugin was actually causing, which helps determine whether it's worth troubleshooting further or simply abandoning.
- Check the plugin's support forum or changelog for known compatibility issues with the current WordPress/WooCommerce/PHP version combination.
- Test the plugin again on a staging copy before reinstalling on live, if it's genuinely needed and a fix or workaround is found.
- Confirm plugin compatibility more carefully before installing new plugins directly on a live production site going forward.
Need this diagnosed properly, or a safer plugin evaluation process set up? See WooCommerce fixes.