Add Or Remove WordPress Sites In wp-toolkit¶

Use this page when wp-toolkit needs to install a new site, attach an existing WordPress site, detach wp-toolkit management, or remove an installation.

Add A New WordPress Site¶

Use a new install when the destination is empty or intended to become a fresh WordPress site.

1. Log in to cPanel.
2. Open wp-toolkit or WordPress Management.
3. Select Install.
4. Choose the domain, subdomain, or folder.
5. Set the site title and administrator account.
6. Review any plugin, theme, or update defaults.
7. Install WordPress.
8. Sign in to WordPress and confirm the dashboard loads.

Attach An Existing WordPress Site¶

wp-toolkit may detect WordPress sites automatically. If it does not, use the scan or attach option if available.

1. Open wp-toolkit.
2. Look for a scan, refresh, or attach option.
3. Select the site path if wp-toolkit asks for one.
4. Confirm the detected domain, path, and WordPress version.
5. Open the site details and verify the admin URL.

Attach or scan does not move the site. It only adds the existing install to wp-toolkit management.

WP-CLI Equivalent: Install A Site¶

Use WP-CLI from the destination folder when the location is empty and intended for a new WordPress installation.

wp core download
wp config create --dbname=DB_NAME --dbuser=DB_USER --dbpass='DB_PASSWORD' --dbhost=localhost
wp db create
wp core install --url='https://example.com' --title='Site Title' --admin_user='adminname' --admin_password='strong-password' --admin_email='admin@example.com'

Replace the database name, database user, password, URL, title, and admin email with the real values for the site.

WP-CLI Equivalent: Confirm An Existing Site¶

Attach and detach are wp-toolkit management actions, so WP-CLI does not have a matching command for that cPanel-side tracking. WP-CLI can still confirm the WordPress install that exists at a path:

wp core version
wp option get siteurl
wp option get home

Detach A Site From wp-toolkit¶

Detach means wp-toolkit stops managing the site. It should not delete the website files or database.

Use detach when:

• The site should remain online but not be managed by wp-toolkit.
• wp-toolkit detected the wrong copy.
• A staging copy should not appear in wp-toolkit anymore.
• Support asks for wp-toolkit management to be removed.

After detaching, confirm the public site still loads.

Remove A WordPress Installation¶

Remove is different from detach. Removing an installation can delete site files, the database, or both depending on the options shown.

Before removing:

1. Confirm the domain and installation path.
2. Confirm whether the site is live, staging, abandoned, or duplicated.
3. Create a backup if any part of the site may be needed later.
4. Review whether the database, files, and uploads will be removed.
5. Remove only the intended installation.

WP-CLI Equivalent: Prepare For Removal¶

WP-CLI can export the database and remove the database contents, but it does not replace the judgment needed before deleting website files.

wp db export ~/example-before-removal.sql
wp db drop --yes

After the database export is safely stored, remove files only after confirming the current folder is the intended WordPress document root. If there is any uncertainty about the path, stop and contact Fused before deleting files.

After Adding Or Removing¶

Check:

• Public URL.
• WordPress admin URL.
• SSL.
• Database name and document root.
• Any redirects or DNS records tied to the site.

Return to wp-toolkit