How to Forcefully Update a Plugin in WordPress?

Replace the plugin’s files in cPanel File Manager, then reactivate it in WordPress. This bypasses a stuck Update button and fixes a half‑completed update.

Before you start

• Have cPanel access and a WordPress administrator login.
• Download the latest plugin ZIP from the official source only, for example the plugin’s WordPress.org page or the developer’s site.
• Make sure there is enough free disk space in your hosting account to upload the ZIP.

Step 1: Take a quick backup in cPanel

This protects you if anything needs to be rolled back.

1. In cPanel, open Backup or Backup Wizard.
2. Create and download at least a Home Directory backup and the site’s database backup.

Step 2: Deactivate the plugin in WordPress

This prevents front‑end errors while you replace files.

1. In WordPress Admin, go to Plugins.
2. Click Deactivate for the problem plugin. Do not click Delete, as that can run the plugin’s uninstall routine and remove its data.

Step 3: Upload the fresh version in cPanel and replace the old folder

This replaces the plugin’s code with the new version.

1. In cPanel, open File Manager and go to public_html/wp-content/plugins.
2. Safety net: find the plugin’s folder and rename it to plugin-name.old. This lets you undo the change.
3. Click Upload and send the new plugin ZIP into wp-content/plugins.
4. Back in File Manager, select the ZIP and click Extract. Confirm the extracted folder name matches the original plugin folder name. If it does not, rename it to match.

Step 4: Reactivate and test

This brings the plugin back online.

1. In WordPress Admin, go to Plugins and click Activate on the plugin.
2. Check key pages and features that rely on the plugin.

Step 5: Roll back if needed

This restores the previous working version.

1. In cPanel File Manager, go to wp-content/plugins.
2. Rename the new plugin folder to plugin-name.new, then rename plugin-name.old back to the original folder name.
3. In WordPress Admin, refresh Plugins and Activate if required.

If it does not work

• Update button does nothing: your wp-config.php may set DISALLOW_FILE_MODS to true, which disables installs and updates in the dashboard. Replacing files in cPanel, as above, bypasses that block. If you need help reviewing wp-config.php, open a support ticket.
• “Could not create directory” or “Could not copy file”: fix filesystem permissions and check disk quota, then repeat the cPanel method. WordPress recommends 755 for directories and 644 for files. If you want us to check permissions or free space on the server, open a support ticket.
• Stuck on “Briefly unavailable for scheduled maintenance…”: in cPanel File Manager, delete the .maintenance file in your site’s document root, then reload the site.

What next

If you want us to do the replacement or check server permissions and space, open a support ticket and include your site URL, the plugin name and version, and what you saw on screen. Running WordPress on a VPS and want to handle server‑level fixes yourself? Start with our VPS guides, or see our UK locations on our London VPS page.