• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Wordpress 1-click-install installs in /wordpress instead of /

Bitpalast

Plesk addicted!
Plesk Guru
TITLE:
Wordpress 1-click-install installs in /wordpress instead of /
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:
CentOS 7.3, 64-Bit, Onyx 17.5.3 latest MU, latest Wordpress toolkit
PROBLEM DESCRIPTION:
When Wordpress is installed with the pre-configured 1-click-installation from the apps repository, it installs into a /<domain>/wordpress subdirectory. When the user opens his homepage afterwards, the homepage document root directory is still pointing to /, not to /wordpress. The user then only sees the Apache test page, but not his Wordpress page.

The document root directory cannot be changed afterwards to /wordpress, because Plesk recognizes that an application is installed in that domain. So Plesk prohibits the modification of the document root path.

In order to use the website with Wordpress, the user is forced to create an .htaccess file in /<domain> to forward all requests one level deeper to /<domain>/wordpress.​
STEPS TO REPRODUCE:
1. Create any domain in a subscription.
2. Go to "applications", select Wordpress and click "install" (the 1-click install, not the one with additional configuration options)​
ACTUAL RESULT:
Wordpress gets installed into /<domain>/wordpress.​
EXPECTED RESULT:
Wordpress gets installed into /<domain>
OR
In addition to the installation, the document root path must be auto-changed to /<domain>/wordpress.​
ANY ADDITIONAL INFORMATION:
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:
Confirm bug
 
@Peter Debik It seems that WPT believes that there is WP already exists in docroot. Most probably that there is only one wp-config.php
It is possible if you had WP there before. Please check what you have in docroot now?
 
That is possible, I did not check that before redoing the installation in the / directory. I have just created another install on another account, and there it did work correctly in the / directory. So it is obviously not a bug, but a feature.

Case can be closed.
 
Back
Top