How to Enable or Disable WordPress Plugins via the Database
If your WordPress admin login page displays only a blank screen, it may be caused by one or more installed plugins. This commonly occurs when a plugin is incompatible with the active theme. It can also happen after a WordPress update, as plugin developers may not always update their plugins immediately to maintain compatibility with the latest WordPress features and security updates.
To determine whether a plugin is causing the issue, temporarily disable all plugins, then re-enable them one at a time to identify the problematic plugin.
In this article, we will discuss the following:
Method 1: Through the Plugins Tab
This is the easiest method. Disable all plugins through your Customer Portal, then re-enable them one at a time until the issue reappears.
Step 1: Disable All Plugins
- Log in to your Customer Portal.
- Go to Websites from the left navigation menu.
- Click Manage Site next to the website you want to manage.

- Click the Plugins tab in the top menu.
- Use the toggle on the right to disable each plugin, one at a time.
- Once all plugins have been disabled, refresh your website. You may also want to clear your browser cache.
Step 2: Find the Plugin Causing the Issue
- Re-enable your plugins one at a time.
- Reload your website.
- Repeat steps 1-2 for each plugin until the issue returns. The plugin you turn on last is likely the cause.
- Turn off that plugin and turn the rest back on.
- You may update that plugin, contact its developer, or replace it with an alternative.
Method 2: Through the Database
Use this method if you can't disable your plugins in the Customer Portal (Method 1) or WordPress Dashboard. You'll disable all plugins at once by editing your WordPress database. Your plugins stay installed, and their settings are kept.
Step 1: Determine the Database Name
Identify the database associated with the WordPress installation you want to modify.
- Log in to your Customer Portal.
- Go to Websites from the left navigation menu.
- Click Manage Site next to the website you want to manage.

- Navigate to the Files & Access tab.
- Find the File Manager, then click the Manage button.

- In the left pane, go to public_html (or the domain's document root).
- Click Settings in the top-right corner.
- Select the Show Hidden Files (dotfiles) checkbox. By default, the WebRoot (public_html or www) option is selected.

- Click Save.
- Right-click wp-config.php and select View. You can also click the View button found in the top-right corner.

-
Take note of the database name. It looks similar to this:
define('DB_NAME', 'domain_wrdp1')(The first part is a short form of your domain or cPanel username.)
Step 2: Disable All Plugins
- In cPanel, click phpMyAdmin in the Databases section.

- In the left menu, click your database name from Step 1.
- Click the wp_options table. If your site uses a custom table prefix, the table may be named differently, such as wpxy_options.

- In the option_name column, find the line named active_plugins. (You may have to click the > at the bottom of the page to view more columns.)

- Click Edit on the active_plugins row. The option_value box shows something similar to this:
a:5:{i:0;s:35:"add-from-server/add-from-server.php";i:1;s:25:"age-verify/age-verify.php";i:2;s:19:"jetpack/jetpack.php";i:4;s:69:"simple-full-screen-background-image/simple-full-screen-background.php";i:6;s:27:"wp-super-cache/wp-cache.php";} - Select all of the code in the box, cut it, and paste it into a text file. Save the file on your computer.
- Once the code has been removed, click Go.
All plugins are now disabled.
Step 3: Isolate the Plugin Causing Issues
Re-enable your plugins one at a time to identify which plugin is causing the issue.
- Visit your WordPress admin login page, reload it, and log in.
- Go to Plugins > Installed Plugins. To know where to find your WordPress plugins, you can use this video as a guide.
- Click Activate under one plugin, then reload the page where the issue appeared.
- Repeat step 3 for each plugin until the issue returns. The plugin you activated last is likely the cause.
- Deactivate that plugin and activate the rest. Then update the plugin, contact the developer, or replace it with an alternative.