Stop Plesk managing WordPress without removing WordPress files?

[Kroptokin]

I used the new WordPress Toolkit to install Wordpress.

Now I don't want it. Chiefly because it prevents me changing the document root. Once you've installed an app Plesk won't let you change the document root under Hosting Settings. And now i want to start making quite manual changes e.g uploading other 'apps' and switching back and forth etc. (The feature would be fine if I wasn't planning to mess about like this).

In the WordPress Tab there is a button for 'Remove'. I assume this will remove the app and all the files. Obviously I can copy the files somewhere and then do 'Remove' and then put them back

But i am just wondering if there is an easy way to tell Plesk "Ok. I used the WordPress toolkit to install WordPress and that was great. But now I want to manage it on my own. Can you stop managing it please?"

With thanks

--Kroptokin

 

[custer]

Hi Kroptokin,

If you've installed WordPress manually and then added it to WP Toolkit via "Scan", then you can go to that WordPress instance and click "Remove" to remove the instance from the list. It will continue working as usual, the only caveat is that if you click "Scan" again, it will be added again (we're working on fixing that in upcoming releases).

However, if you've installed WordPress via APS, you cannot remove it from the list to manage it manually without completely removing it from the server.

May I ask you why do you need to change the document root for already installed applications? What is the scenario that requires "messing about" with them?

 

[Kroptokin]

Thanks Custer. I think I installed it via APS.

The scenario is that I have a web site running WordPress. Some other developer has developed a new WordPress site on his development server and now wants to install it to the same domain as ours. He plans to do this by FTPing the files. Because we don't know what his work will look like we want to keep both sites. So I've told him to put his files in a separate directory. If we like his work we'll just change that to be the document root. If not we'll leave it as it is. In either case we need to change back and forth to preview. In short the answer to your question is we want to run two WordPress 'applications' on the site and switch back and forth between them.

(Maybe you will tell me that the WordPress ToolKit can handle this scenario?)

Thanks

Justin

 

[UFHH01]

Hi Kroptokin,

best practice would be to install a subdomain for the developper ( i.e.: dev-blog.domain.com ) using the same directory structure and using a copy of the original database. With this way, you always have the choice to compair webserver configuration files, find misconfigurations for needed webserver rewrites and used plugins and you can always update the copied database to an actual copy, with a few clicks from the "live" database. You are able to handle both blogs over the wordpress toolkit, if you want to, as custer described already.

You are sure as well able to remove a wordpress installation ( installed over APS ), without loosing the content or the database - just copy the entire content to a backup folder and use the feature "copy database" in your database options, before you use the command "remove" over the wordpress toolkit. After you removed wordpress over the toolkit, just restore the content from your backup - folder to the original path and either rename your copied database ( and db - username and password ) to the original data, or make another copy with the initial data over the Plesk Control Panel in your database - settings for the domain. As an alternative, you could as well change the database - configuration settings at your worpress file "config.inc.php" and leave out the part to re-copy your database.

 

[Kroptokin]

Thanks UFHH01. Ok. Using sub-domains is the best approach in these kinds of cases. And also thanks for reminding me to copy the database before Removing the app. I probably would have forgotten. (Though that said I'll probably try scanning and then using the WordPress ToolKit to manage both first).