WP Toolkit: manage WordPress from cPanel

WP Toolkit, called WordPress Toolkit in earlier versions, lets you manage WordPress installations from cPanel. The features available depend on the configuration and licence; do not assume a Deluxe or Smart Update option is included just because it appears in a guide.

The WP Toolkit for cPanel reference describes how to access it and its availability. Open WP Toolkit in cPanel and check the selected installation before any action. If you also use Softaculous WordPress Manager, coordinate updates and tasks to avoid duplicates.

Adding existing installations

Use Scan to find existing WordPress installations. Confirm the URL, root and version of what is detected. Registering a website lets you manage it; it does not mean the tool has repaired its content or checked all its integrations.

Guided WordPress installation

In Install, choose the domain, an empty path, HTTPS, language and credentials. Review the update options and the plugin/theme set if it offers one. Do not select a folder that already contains another website.

After installing, open the front end and the admin area and check the certificate. Keep the credentials in a password manager and remove sample components you do not need.

Smart Update

If available, Smart Update runs checks on a copy to help detect problems after updating. Review the report and visual differences before applying changes.

It does not replace testing a purchase, email, login or private integration. A redirect that sends the clone back to production can stop the check from working as you expect. Keep a backup and a rollback procedure even if the report is favourable.

Managing updates and status of plugins, themes and core

The global views let you work on several sites at once. Check the scope of the selection: bulk updating or deactivating can affect different projects.

For each installation, review dependencies and compatible versions. A plugin being up to date does not prove it is compatible with all the others.

Cloning WordPress

Clone creates a copy of files and data in another destination. Check that it has its own database, protect access and replace production payments, email, tasks and external connections. Sharing a storage key or a cache instance can make two installations interact even if their SQL databases are different.

Copy data

This action replaces files or data in the destination with those from the source. It does not automatically merge later writes from production. Copying the clone's database can delete orders, users and recent changes.

Keep a recoverable backup of the destination, select exactly which files and tables and rehearse the same set on a recent copy. Related tables may need to be handled together; a partial selection is not safe by definition.

Control writes during the switchover, including APIs, cron and external services. Check the front end, admin area, a test purchase and the logs before reopening. If it fails, restore the planned consistent set while preserving any later data that should be kept.

Security scan

Review each proposed measure and its compatibility. A scan with no warnings does not prove the absence of malware or vulnerabilities in every component. Apply changes with a backup and check the affected features; do not enable every restriction without reading what it does.

Administrator password recovery and change

WP Toolkit lets you reset a password; it does not reveal the old one. Log In uses the integration's access. Protect cPanel too, because access to it can allow you to manage WordPress.

After an intrusion, reset credentials and review sessions, users and additional access; logging in to the admin area does not by itself close the incident.

Management tools

See the cron guide before changing how it works. Check the effects of authentication on monitors, tasks and callbacks.

Maintenance mode

Customise the notice and check which visitors and paths are restricted. Do not assume it stops all writes from cron or integrations. When you finish, turn it off and test in a fresh session.

Backups

In Backup / Restore, review the date, content and destination. An on-demand backup can take up space in the account and is no substitute for a retention policy. See also the hosting backups.

Before restoring, identify which recent data will be overwritten and check that you can recover the set you need. Keep evidence of the result and check the application before considering it recovered.