Note: This article has the reference to the issue with the fix available:
- #EXTWPTOOLK-2208 "WordPress Toolkit does not stealthily install WordPress in a subdirectory anymore if the target domain already has an /index.php file."
- WordPress Toolkit 3.5.3 11 December 2018
No subdirectory is specified in Domains > example.net > Install WordPress menu (or in the WordPress > Install), however, the instance is installed into
/wordpresssubdirectory without any warnings:
/is specified as the target directory in Domains > example.net > Install WordPress menu, the installation cannot be started due to the error:
PLESK_ERROR: This directory cannot be used because it contains files that will be overwritten with their data lost. You can manually clear the folder and perform the installation again.
index.phpexists in the domain's Document Root, as can be seen in the Domains > example.net > File Manager:
index.php is present in the domain's Document Root, and therefore WordPress Toolkit automatically installs the instance to the subdirectory to prevent overwriting the file.
This behavior is considered to be a bug #EXTWPTOOLK-2208.
Update the WordPress Toolkit extension: How to update Plesk extensions
Navigate to Domains > example.net > File Manager
Rename the existing index.php file by clicking on the button and then Rename
Install the WordPress in Domains > example.net > Install WordPress menu with no subdirectory specified