I am attempting a new install of XOOPS (tried both 2.0.7.3 and 2.0.9.2), and when going through the install pages, the error that comes back is:
Could not connect to the database server.
This error only occurs with a non-root user. The root user successfully completes the install and I can log into the XOOPS site.

I also have a working XOOPS site that uses a non-root user. I have also set up the new non-root user to only be able to use its own database, the same way as the other working non-root user.

So, after completing the install with the root user information, I change the mainfile.php information to use the non-root user login. That problem then says:
This page cannot be displayed due to an internal error.
If you are the administrator of this site, please visit the XOOPS Troubleshooting Page for assistance.
Error [Xoops]: Unable to connect to database in file class/database/databasefactory.php line 34
So, then I change back to the root user, and it all works again.

For obvious reason, I don't want to keep the site running with the root login.

I have deleted, added, flushed, etc, the user tables, but I can't figure out this one.

To make this more interesting, I can log in tot he DB through the command line with the non-root user information I want to use and select the correct DB and show the tables, etc.

Any ideas where lies the problem?

thanks
eric

what versions of php and MySQL etc are you using?

Quote:
php 4.2.2 and MySQL 4.1.7.

Both unchanged since the original working install of Xoops.

the problem as i see it is that php 4.2.2 is incompatible with the new 4.1.x versions of mysql..

the password hash was changed..

and previous versions will not be able to connect using a non-root password..

i would suggest either upgrading php to 4.3.10 or drop MySQL down to 4.0.x , you could also try MySQL 4.1.9 aswell..

or you can try using sql administrator and click security and then tick the box for 'use old password method'

you would then need to reset your password to MySQL (8 - 10 chars max)

or you could set an account up and tell MySQL to use the old password method for that account..

for example:

mysql> UPDATE mysql.user SET Password = OLD_PASSWORD('newpwd')
-> WHERE Host = 'some_host' AND User = 'some_user';
mysql> FLUSH PRIVILEGES;


OLD_PASSWORD doesn't mean ur old password.. it's telling sql to use the old password hash method..

Quote:

I was hoping I would not need to do the upgrade. But, I guess it is for the best.

For the time being, I could get MySQL installed without too many dependency headaches.

I will work on the remaining dependencies (php, apache, etc.)

Thanks for your help!
eric