• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved Fix definers if MySQL user is renamed during migration

nineproof

New Pleskian
When Plesk Migrator has to rename a MySQL user during migration due to a conflict,
showing this warning message in the log:

MySQL database user with the name 'wordpress_0' already exists on target server. Database user 'wordpress_0' from the source server will be renamed to 'wordpress_02' on the target server.

the DEFINER of stored procedures, views, AFTER triggers, events won't be changed accordingly, causing disruption of the migrated site, with errors like:

The user specified as a definer ('wordpress_1'@'%') does not exist.​

Seems the the issue won't involve just BEFORE triggers. No warnings are shown in the log.
 
Hello, we have created Plesk Migrator issue PMT-4065. It will be investigated and fixed in future releases if will be confirmed.
 
Hello,

We have investigated this behavior and confirmed more one software issue PMT-4073.
The issue PMT-4065 describe slightly different situation.
 
Back
Top