• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Migrating WordPress-MU to webroot for enabling MultiSite required?

Thalon

New Pleskian
Hi,

I need to move my WordPress-subdirectory-installation in own 'wp_mu'-folder into the httpdocs-root-dir, so I can enable WordPress-Multisite and create a network of Sites.

/var/www/vhosts/mydomainname.de/httpdocs

I am on a Strato physical dedicated server hosting, running Ubuntu Server 10.04 LTS and Plesk Panel 10.0.

My Questions are:

1. Is it really required to move my WP-MU install into the upper-directory? Or are there "plesky" workarounds, I beliebve so as WordPress is the most commonly used blog software.

2. if required: Which of the following Plesk-related files and directories are just placeholders for the default generated Plesk-site, and can I safely delete?

inside '/var/www/vhosts/mydomainname.de/httpdocs/':
wp_mu/
test/
plesk-stat/
picture_library/
img/
css/

and files:
.htaccess
index.php
favicon.ico
index.html


From the directories listed above, which ones I can safely delete:
plesk-stat, img, picture_library, css: I think so, but wanted to ask the professionals here.

but with the 'test'-directory I am not so sure, are there availability/monitoring checks about the subscription performance, testing the supported services (PHP, Python, SSI, Perl, SSL, ...)

This I really do not know. Please advise here, it is very urgent, as client are pushing.

Third question:

How to install WordPress-MU v3.0.5 under Plesk, so I can properly account the data, traffic and domain-names for each customer/subscription properly, as it is done with Plesk?

So far, all customers requiring a blog, are handled via a single virtual "customer", the domain switching is done with a WordPress-MU plugin called 'WP MU Domain Mapping Plugin'.

Any others with hints for me? Some pointer to a good tutorial/thread how to do it the Plesk way?

Thanks
 
Folder test can be deleted.

If you have a look on the self generated page for the domain (plesk page) you can find some icons for tests like php and so on ...

The pages and scripts are located in the folder test - so they belong like the the img folder only to the self generated first page structure.

I deleted the files and everything is woriking fine until now.
 
Back
Top