Install scripts issue

Submitted by helpmin on Sun, 12/11/2011 - 04:29

I am trying to figure out what the best way is to upgrade phpmyadmin (which is highly recommended because of the many security issues) and noticed the following problem (phpmyadmin already installed):

Install again ... Failed to install script : Another script is already installed in /home/yoonique/public_html/phpmyadmin.
Click on return to previous page
Error: Failed to install script : Scripts can only be installed into virtual servers with a home directory and website
Click on return to previous page
Error: Scripts can only be installed into virtual servers with a home directory and website click on return to previous page
Error: Failed to install script : Scripts can only be installed into virtual servers with a home directory and website

and so on

The other question is. How do you actually upgrade an existing installation with virtualmin (for example phpmyadmin)?

Status: 
Closed (fixed)

Comments

Submitted by andreychek on Sun, 12/11/2011 - 08:11

Howdy -- it sounds like you may be trying to install a script over-top of an existing installation, rather than upgrading it.

If that phpMyAdmin installation was installed using an Install Script, you can upgrade it by going into Virtualmin, choose that domain from the drop-down list, click Install Scripts, and on the resulting page, you'll see a list of all the Install Scripts that have been installed.

Just click the checkbox next to phpMyAdmin, and click the "Upgrade Selected Scripts" link at the bottom of the page.

Submitted by helpmin on Mon, 12/12/2011 - 02:50

Yes, correct. I tried that for testing purposes and discovered that "infinite cycle bug".

You are correct again, you can upgrade for example by entering the latest version number in the unsupported version field.

Everything works :-) (except for the infinite loop described above, which is only a minor "thing")

Submitted by JamieCameron on Mon, 12/12/2011 - 14:09

I'll fix that loop in the next Virtualmin release..

Submitted by Issues on Mon, 12/26/2011 - 14:18

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