The recent update to phpMyAdmin 4.0.5 brought many unwelcome interface changes to the central phpMyAdmin that is accessed through WHM>SQL>phpMyAdmin
Changing this configuration is possible in phpMyAdmin on a session only basis, which is only helpful in limited circumstances.
Changing this configuration is possible in /usr/local/cpanel/base/3rdparty/phpMyAdmin/config.inc.php
However every upcp update will overwrite this file - I found this out only after spending half an hour editing only to find everything lost the next morning.
The recommended way to achieve this is by configuration storage. The process to set this up is hard to follow in many instances, for instance running examples/create-tables.sql will give an error on one of the tables it is trying to create, and any small mis-step can easily lead to being locked out of your WHM>SQL>phpMyAdmin (I found this out at the school of hard knocks as well).
What would be great is one of two things.
- Have the table for configuration storage already setup.
- Clear cPanel documentation on how to do this.
Thanks for considering this.
Jim Longo
I like this idea 
One of the recommended ways to accomplish this, without actually satisfying the request, is to make your desired changes to the configuration file, and then replace the file after the nightly updates. You may run into problems when an update happens between major versions (as will happen on upgrade from version 62 to 64), but between minor versions you should be fine.
Once you are satisfied that the configuration file is how you want it, copy the configuration file to a safe location (e.g. /root/custom_configuration).
Next create the postupcp file, if it doesn't already exist.
Finally add the necessary commands to copy your configuration file in place. Here's one untested example:
Test the script after you create it. upcp will call that script near the end of every update. I'd recommend putting some output or comments in the script so you have a reminder of what it is doing.
You might also want to add some logic that would retain the cPanel-provided configuration when the postupcp script is run.
One of the recommended ways to accomplish this, without actually satisfying the request, is to make your desired changes to the configuration file, and then replace the file after the nightly updates. You may run into problems when an update happens between major versions (as will happen on upgrade from version 62 to 64), but between minor versions you should be fine.
Once you are satisfied that the configuration file is how you want it, copy the configuration file to a safe location (e.g. /root/custom_configuration).
Next create the postupcp file, if it doesn't already exist.
Finally add the necessary commands to copy your configuration file in place. Here's one untested example:
Test the script after you create it. upcp will call that script near the end of every update. I'd recommend putting some output or comments in the script so you have a reminder of what it is doing.
You might also want to add some logic that would retain the cPanel-provided configuration when the postupcp script is run.
Another item that would be nice to set in phpMyAdmin is to enable SSL for the connection to the database server, especially when remote MySQL/Mariadb profile is in use.
Another item that would be nice to set in phpMyAdmin is to enable SSL for the connection to the database server, especially when remote MySQL/Mariadb profile is in use.
Replies have been locked on this page!