Resolved Avoid installing WordPress when migrating a subscription from another Plesk

[Fran Silva]

Server operating system version

AlmaLinux 9.5 (Teal Serval)

Plesk version and microupdate number

Plesk Obsidian 18.0.69 Update 3

I have searched in forum and Plesk documentation but I don't see a way to migrate a subscription from the tools (old Plesk Migrator extension), it doesn't install WordPress.

When I migrate a subscription with a PHP website, I install WordPress on top of the PHP application.

In the migration configuration I do not have the option Adjust application settings checked, nor do I see any option to prevent the installation of APS.

 

[Sebahat.hadzhi]

Hello, @Fran Silva . I am afraid, I unable to get a clear idea of what the issue is, sorry. Plesk Migrator should move the applications (be it WordPress or a custom PHP application) exactly as they are on the destination server. It is not supposed to install/un-install anything.

I am assuming the issue is happening after the migration, but please provide as many details as possible.

 

[Fran Silva]

For example if I finish a migration from Plesk Obsidian 18.0.61 CentOS Linux 7.9.2009 (Core), where there was no WordPress installed on the domain, at the end of the migration Plesk installs Wordpress, it is notified in the interface at the end, it should not install it.

 

[Fran Silva]

Hello @Sebahat.hadzhi
I hope I have explained better, I still have not solved the problem, when migrating from another Plesk without WordPress installed in the source subscription, the target Plesk installs WordPress in the subscription.

 

[Sebahat.hadzhi]

Thank you for the update. I am afraid, I still have no clear understanding what's going on the server. What I tried in an attempt to reproduce the issue is transferring a non-WordPress (Joomla) website from a source CentOS 7.9 server to a target AlmaLinux 9.5 server through the Plesk Migrator extension. I am unable to reproduce the described behavior. Please note that the test I ran is not on Plesk 18.0.61 as this is a severely outdated version. Just to make sure we are on the same page, please provide detailed step-by-step instructions on how can we attempt to reproduce the reported issue.

 

[Fran Silva]

I think the problem is not in the migration operation, rather it seems when the subscription is created. I have tried creating a subscription instead of migrating it and it has installed Wordpress for me even though I have chosen to use a blank website.

 

[Fran Silva]

The configuration of the service plan is the one that determines that WordPress is installed when creating the subscription, in the additional services of the hosting plan configuration it is possible to define (by default) that WP Toolkit installs WordPress.

It was therefore in this configuration that the automatic installation of WordPress is activated.

Thank you very much for your attention and interest in this matter.