installer script for Joomla 1.0.15 fails to install if the virtual server's password has been changed but not the MySQL password

Submitted by nant on Fri, 09/02/2011 - 08:13

installer script for Joomla 1.0.15 fails to install if the virtual server's password has been changed but not the MySQL password.

Joomla 1.7 installer runs fine in that condition, but joomla 1.0.15 installer appears to be "backwards-compatibility wise broken": Looks like old installer script for Joomla 1.0.15 needs to be udpated to the new method of getting database password

Status: 
Closed (fixed)

Comments

Submitted by beat on Fri, 09/02/2011 - 08:36

Hi Joe and Jamie, btw, Nick (nant) works with me, so that you can see all the Virtualmin Pro licenses. ;-) And i could confirm the issue.

Submitted by JamieCameron on Fri, 09/02/2011 - 10:39

Was the password change done within Virtualmin? The Joomla installer should support different DB and domain passwords, but only if the change was made at Edit Databases -> Passwords, so that Virtualmin knows about it..

Submitted by beat on Fri, 09/02/2011 - 12:44

The hosting plan is set to not change the database password when the webmin password is changed. Database password hasn't been changed, but webmin's has.

Joomla 1.7 installs fine. Only Joomla 1.0.15 doesn't.

Joomla 1.0.15 maybe has an older virtualmin installer that takes the webmin password for database ?

I remember something related to database password in joomla installer was fixed in the installer API around a year ago...

Submitted by JamieCameron on Fri, 09/02/2011 - 12:54

The installer code uses the same password for both Joomla 1.0.15 and 1.7 ..

What is the exact error message you are getting when installing (or after) ?

Submitted by nant on Fri, 09/02/2011 - 13:15

Beat asked me to post error message when trying to install Joomla 1.0.15:

Install Script
In domain j1015.cbdemosites.com Found http://joomlacode.org:80/gf/download/frsrelease/6828/22537/Joomla_1.0.15... in cache ..

Configuring Apache PHP settings .. .. done

Applying web server configuration .. .. done

Now installing Joomla version 1.0.15 ..

Database connection failed : DBI connect failed : Access denied for user 'j1015admin'@'localhost' to database 'j1015admin_joomla' 1360.

.. failed! See the error message above for the reason why.

<- Return to list of scripts

Submitted by nant on Fri, 09/02/2011 - 13:24

And here is successful Joomla 1.7 script run messages:

Install Script
In domain j1015.cbdemosites.com Found http://joomlacode.org:80/gf/download/frsrelease/15278/66554/Joomla_1.7.0... in cache ..

Configuring Apache PHP settings .. .. already done.

Now installing Joomla version 1.7.0 ..

Joomla installation complete. Go to http://j1015.cbdemosites.com/administrator/ to manage it.

More information on using this script can be found at http://joomlacode.org/.

The initial administration login is j1015admin with the password XXXXXX

.. done

Re-loading Webmin .. .. done

Submitted by JamieCameron on Fri, 09/02/2011 - 13:23

That is really odd ... were both installs using the same database, and in the same domain?

The code in the installer that runs the SQL is the same for all Joomla versions.

Submitted by nant on Fri, 09/02/2011 - 13:35

Yes, both installs use the default script settings which is set to create a new database. No databases exist on this domain before script running.

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

Any chance I can login to this system myself and try a test install to see what is going on?

Submitted by nant on Fri, 09/02/2011 - 15:43

How can I privately send you credentials?

Submitted by JamieCameron on Fri, 09/02/2011 - 17:19

Ok, I see the problem now .. the error happens when you install Joomla 1.0 and are creating a new DB at the same time. The work-around is to create the DB first, then select it when installing..

I will also fix this in Virtualmin 3.88

Submitted by beat on Tue, 09/06/2011 - 17:11

Thank you Jamie, really appreciated :-) Beat

Submitted by Issues on Tue, 09/20/2011 - 18:23

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