• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

MySQL autoincrement dropped!

B

blank

Guest
Did a migration from Plesk 8.2 to 8.3, and now all databases seem to have lost the autoincrement option on the columns that should have it. Anybody else run into this problem?
Also, all databases charsets have changed to UTF-8, but I believe this is due to MySQL version change and is not a biggie.

At the moment the sites have been running on the new Plesk for quite some time so they are out of synch from the old server and doing new migration is impossible. I guess the only way is to take dumps of databases on both servers, AWK&diff the schema parts of dumps to detect changes using script & fix...

So much for smooth transition, argh!!
 
OK quick search on the forums revealed that this "problem" has been there since 2006 at least.. Still not officially fixed & have to manually edit Plesk scripts to even make backups work?!

Other users BEWARE!
 
Back
Top