Activate a WordPress Plugin From cPanel

Terminal plus WP-CLI is the shortest route, and it prints a result you can read. Use it when the account has shell access and cPanel shows the Terminal icon under Advanced.

1. In cPanel open Advanced, then Terminal.
2. Change to the folder that holds wp-config.php: cd ~/public_html. If WordPress lives in a subfolder, cd into that folder instead.
3. Run wp plugin list. The name column is the slug you activate, which is often not the plugin's display name.
4. Run wp plugin activate akismet, replacing akismet with that slug.
5. Read it back with wp plugin list --status=active.

You know it worked when the last command prints the plugin with status active and the site loads without a blank page. If a caching plugin is running, clear the WordPress cache before you judge the front end.

Common failure: Error: This does not seem to be a WordPress installation. You are in the wrong directory. Run ls wp-config.php to confirm the folder, then cd again. If Terminal answers wp: command not found, the host has not enabled WP-CLI for shell users; use WP Toolkit or phpMyAdmin instead.

The WP-CLI activation command documents plugin slugs and network scope. If bootstrap errors prevent inspection, --skip-plugins and --skip-themes can help isolate ordinary components; must-use plugins are still loaded. Do not bypass requirements merely to force incompatible code to run.

phpMyAdmin can inspect or restore activation state, but a manual options edit does not run WordPress activation hooks. Prefer WP-CLI or WP Toolkit for normal activation, especially for plugins that create tables or need dependencies.

1. Export the database before inspecting or changing activation state.
2. Read the database name and actual table prefix from wp-config.php.
3. Locate active_plugins in the correct options table and preserve its original value.
4. If corruption caused a lockout, restore a verified value or follow an approved recovery procedure.
5. Once access returns, activate the intended plugin through WordPress or a supported management tool and test its setup.

PHP serialisation uses byte lengths and an array count; copying another installation’s value can corrupt state or load the wrong code. The WordPress activation API also distinguishes ordinary and network-wide activation.

Diagnose a WordPress lockout from logs and recent changes before disabling plugins. Preserve the active-plugin list and database. If a plugin conflict is plausible, disable the suspected plugin first; disabling all ordinary plugins is a temporary diagnostic step, not a confirmed cause.

1. With Terminal, run wp plugin deactivate --all in the WordPress folder.
2. Without Terminal, set active_plugins to a:0:{} in phpMyAdmin.
3. Load the site and wp-admin. If both return, a plugin was the cause.
4. Activate one plugin, reload, and repeat until the fault comes back. The plugin that breaks the page is the one to replace.

If the site still fails, inspect logs for theme, must-use plugin, network-active plugin or infrastructure faults. Emptying the ordinary plugin list does not rule out those other causes.