Facebook
Twitter
Jay Versluis
Regular Pleskian
Hello Igor,
I've discovered a bug with Migration Manager - see below:
---------------------------------------------------------------
PRODUCT Plesk Panel, VERSION 10.4.4 (MU9), OPERATING SYSTEM CentOS 6, ARCHITECTURE 64bit
PROBLEM DESCRIPTION AND STEPS TO REPRODUCE
I'm migrating subscriptions from a source with installed applications (in my case WordPress instances). On my source I have a separate DB server as default MySQL server defined. I'm using the same setup on my destination server. In total we're talking about 4 different servers here: two source (main and DB), and two destination servers (main and DB).
ACTUAL RESULT
When I use migration manager to bring a subscription across, the new database gets created on localhost instead of the defined database server.
EXPECTED RESULT
When an application gets created locally, Plesk correctly uses the defined DB server instead of localhost. I would expect Migration Manager to create the database on the defined default DB server too instead of localhost.
ANY ADDITIONAL INFORMATION
Migration Manager also changes two values in the database:
In the table wp_options, both option_id 1 (site_url) and option_id 37 (home) get changed to https://sitename.com instead of http://sitename.com. This results in the migrated site not being displayed properly.
--------------------------------------------------------------
If there's anything I can do to help, please let me know. I will test this with an application other than WordPress (OSticket of PHPlist) to see if the result is different. I will report back.
I've discovered a bug with Migration Manager - see below:
---------------------------------------------------------------
PRODUCT Plesk Panel, VERSION 10.4.4 (MU9), OPERATING SYSTEM CentOS 6, ARCHITECTURE 64bit
PROBLEM DESCRIPTION AND STEPS TO REPRODUCE
I'm migrating subscriptions from a source with installed applications (in my case WordPress instances). On my source I have a separate DB server as default MySQL server defined. I'm using the same setup on my destination server. In total we're talking about 4 different servers here: two source (main and DB), and two destination servers (main and DB).
ACTUAL RESULT
When I use migration manager to bring a subscription across, the new database gets created on localhost instead of the defined database server.
EXPECTED RESULT
When an application gets created locally, Plesk correctly uses the defined DB server instead of localhost. I would expect Migration Manager to create the database on the defined default DB server too instead of localhost.
ANY ADDITIONAL INFORMATION
Migration Manager also changes two values in the database:
In the table wp_options, both option_id 1 (site_url) and option_id 37 (home) get changed to https://sitename.com instead of http://sitename.com. This results in the migrated site not being displayed properly.
--------------------------------------------------------------
If there's anything I can do to help, please let me know. I will test this with an application other than WordPress (OSticket of PHPlist) to see if the result is different. I will report back.
Last edited:
