phpMyAdmin installed from a template has access to only the database of virtual server it was installed on

We have to install phpMyAdmin on every Cloudmin based Virtualmin guest system. To automatize this we created a separate template and selected "phpMyAdmin" script to auto-install on "Default script installers" page. It works great, but the problem is that phpMyAdmin auto-installed this way has access to only its own database, because there is no "Database to manage" option on "Default script installers" page unlike when installing it manually - we can select "All databases" for "Database to manage".

A request to add such an option to indicate all or specific database(s) on "Default script installers" page of Virtualmin templates, please.

Thank you!

Status: 
Closed (fixed)

Comments

The phpMyAdmin installer is a bit of a special case - you need to select "None" in the "Database name" column on the default script installers page. Then it will be granted access to all databases that the user logging in has access to.

Automatically closed -- issue fixed for 2 weeks with no activity.

What if we are installing phpMyAdmin in post creation script and not through a template? The following code works great:

virtualmin install-script --type phpmyadmin --domain db.$VIRTUALSERVER_DOM --version latest --path / --db mysql $VIRTUALSERVER_DB"_db" --user $VIRTUALSERVER_USER --pass $VIRTUALSERVER_PASS >> /dev/null 2>&1

however, when logging into phpMyAdmin shows no database to manage. Is there any additional parameter to make phpMyAdmin installed from the post creation script to see and manage all databases?

If you want to grant phpMyAdmin access to all databases the user can see, just remove the --db mysql $VIRTUALSERVER_DB"_db" flag from that command.

Works like a charm, thanks!