Facebook
Twitterdarealhamsta
New Pleskian
Has anyone switched from the stock MySQL 5.0 to the Plesk-provided 5.5? Did it just work, or were there problems?
-
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.
Switching from MySQL 5.0 to 5.5
- Thread starter darealhamsta
- Start date
darealhamsta
New Pleskian
Thanks abdi. Was this from 5.0 or 5.1? There's a substantial difference between them - MySQL recommend exporting and importing databases, for example - which is why I'm a little concerned. You didn't have any complaints from customers about changes in MySQL responses or anything?
Similar threads
