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

Bug when installing Wordpress custom app

KingSky

New Pleskian
I am using Plesk 12.0.18

When I go to apps and choose to custom install Wordpress, it asks what table prefix you would like to use.

I am migrating a site to a new host, so I choose "wp_" so it will be the same as the current db.

I install then go look at the database and Plesk has randomly generated the table prefix. I thought maybe I'd done something wrong so I removed the installation and tried again. Again I put in "wp_" as the desired table prefix. Look in the database and table prefix is randomly generated "2nUI4qaC4L_".

Why does the custom installation not respect the table prefix entered? Any ideas?

Thanks,
-Kevin
 
I was testing this on a VPS server. I went back to my own dedicated server and the same issue occurs there.
 
Back
Top