• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

MySQL 4 to MySQL 5 migration dropped auto_increment

H

HoneyMonster

Guest
I have just migrated a bunch of domains from a Plesk 7.5 MySQL4 PHP4 server to a Plesk8.1 MySQL5 PHP5 server. To my suprise the Plesk migration manager completed without any errors. Yay was I happy!

Then I noticed that every website was broken as the auto_increment attribute had been removed from the primary key of every table!

Is this likely to be an issue with upgrading MySQL4>5 or a bug in the Plesk migration manager? I assume that the migration manager simply takes a dump of the database and then imports it into the new one.
 
I think this is a big problem with pleskbackup, because I've restored from other machines with no problem.

It just happened to me after a backup and restore. I am ****ing steaming pissed right now.

WHAT GOOD IS A BACKUP THAT DOESN'T PROPERLY BACKUP?!
 
Back
Top