• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be 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.

Databases are inconsistant in Plesk 9.3

M

Michael neese

Guest
My default 1and1 installation on new server last month has these database keys...

horde....latin1_swedish
mysql....latin1_swedish
phpmyadnin...latin1_swedish
psa....latin1_swedish
tortix....latin1_swedish

Whereas, when I create a new database for a new domain, using the plesk interface and database creation functions... after domain is created, before applications are installed, such as Joomla or Wordpress...they are being created using utf8_general_ci...

Should plesk be creating consistent database throughout the system?
Should these databases be converted to make them all either utf8, or swedish latin?
Is there a problem with these inconsistancies?
I have had no luck with backups and restore functions in plesk...could this be an issue that should be adddressed? If so, how to address?
 
Back
Top