PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE
Ubuntu 24.04 (x86_64), Plesk 18.0.81 Update 8, WP Toolkit 6.11.7-10909, WordPress 7.1.4 Multisite.
PROBLEM DESCRIPTION
On 18 November 2026, we retired an additional Plesk host sharing a WordPress Multisite installation and files with other active hosts. We first changed its document root to a separate empty directory, then removed only its Multisite blog and that Plesk host. The shared database still belonged to the parent subscription and was required by the remaining hosts.
STEPS TO REPRODUCE
1. Create subscription parent.lab.test with root httpdocs. Point additional domain keep.lab.test and subdomain retire.parent.lab.test to the same /shared root. Install WordPress Multisite there, with one blog for each host. WP Toolkit must recognize one shared instance bound to both hosts. The database and user belong to the parent subscription.
2. Change only the retiring subdomain's root:
Check that the shared Toolkit instance's path also changes to /retired-empty, although the other host still uses /shared.
3. Remove only the corresponding WordPress blog, as in the incident; the lab used wp_delete_site(2). Restore the .php-version/.php-ini helper files removed by Plesk from the shared root. The shared database was still working at this point.
4. Remove the subdomain and let all background tasks finish:
ACTUAL RESULT
After the root change, the shared Toolkit instance pointed to the new empty directory. On host removal, WP Toolkit removed the shared registration, database user and entire database. The other Multisite websites failed and required a backup restore. The shared WordPress files survived.
Database deletion was asynchronous and completed after the host-removal command had returned successfully. No explicit command to delete the entire database was issued.
The synthetic lab also lost the database, but not on every run. With callback order controlled, the Toolkit subdomain_delete handler deleted the database before either hosting handler was allowed to run. When phys_hosting_delete and phys_hosting_update ran first, only the host binding was removed and the database survived.
EXPECTED RESULT
Remove only the selected host. Preserve the shared installation, database and user still needed by the remaining hosts.
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM
Confirm bug.
Ubuntu 24.04 (x86_64), Plesk 18.0.81 Update 8, WP Toolkit 6.11.7-10909, WordPress 7.1.4 Multisite.
PROBLEM DESCRIPTION
On 18 November 2026, we retired an additional Plesk host sharing a WordPress Multisite installation and files with other active hosts. We first changed its document root to a separate empty directory, then removed only its Multisite blog and that Plesk host. The shared database still belonged to the parent subscription and was required by the remaining hosts.
STEPS TO REPRODUCE
1. Create subscription parent.lab.test with root httpdocs. Point additional domain keep.lab.test and subdomain retire.parent.lab.test to the same /shared root. Install WordPress Multisite there, with one blog for each host. WP Toolkit must recognize one shared instance bound to both hosts. The database and user belong to the parent subscription.
2. Change only the retiring subdomain's root:
Code:
plesk bin site --update retire.parent.lab.test -www-root retired-empty
3. Remove only the corresponding WordPress blog, as in the incident; the lab used wp_delete_site(2). Restore the .php-version/.php-ini helper files removed by Plesk from the shared root. The shared database was still working at this point.
4. Remove the subdomain and let all background tasks finish:
Code:
plesk bin site --remove retire.parent.lab.test
ACTUAL RESULT
After the root change, the shared Toolkit instance pointed to the new empty directory. On host removal, WP Toolkit removed the shared registration, database user and entire database. The other Multisite websites failed and required a backup restore. The shared WordPress files survived.
Database deletion was asynchronous and completed after the host-removal command had returned successfully. No explicit command to delete the entire database was issued.
The synthetic lab also lost the database, but not on every run. With callback order controlled, the Toolkit subdomain_delete handler deleted the database before either hosting handler was allowed to run. When phys_hosting_delete and phys_hosting_update ran first, only the host binding was removed and the database survived.
EXPECTED RESULT
Remove only the selected host. Preserve the shared installation, database and user still needed by the remaining hosts.
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM
Confirm bug.