• 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.

Plesk 10 phpmyadmin bug

HostaHost

Silver Pleskian
Parallels, is this a known issue?

In Plesk 7, 8 and 9, when you opened phpmyadmin via the DB Web Admin button, you'd get a pop-up window for managing that database. If you tried to then go back and open DB Web Admin for a second database, it would not open a new window, it would refresh the first one.

In Plesk 10.4 (all MU's applied) each db opens a new window, however, what you don't know, is that the first window has now become associated with the second database, so if you had a query written but not executed in that first window, or you drop a table, well, bad news, you just ran that query against the second database instead of the one the window was supposed to be for.

I would report this as a bug via support but I don't want to take a chance of losing an incident since Parallels penalizes their partners for reporting issues if someone else beat them to it.
 
Back
Top