I wasn't quite sure where to place this, but I wanted to document a problem I've recently found (which I hope is related to my hosting and not through a fault of my own).
I've used the Enthusiast script for several years and can connect fine to the old database, but I've recently downloaded the script for a new site I'm working on.
I followed the steps accordingly and included the (nearly identical) database information into the configuration file. Now I'm getting this error:
My first thought was that I was incorrectly accessing the database, so I repeatedly checked that all permissions were granted, that the file was chmod'ed to the same permission as the old config file and that I didn't mispell a word in the connection lines. That didn't work.
Then I tried transferring the files from the older script to the new folder/site. This was under the assumption the new downloaded script had an improper code somewhere. After the transfer I was able to access the old database from the new site.
To add, both the older database and the newer database for the scripts have the exact same user (and thus assumedly the same pw). The only difference between the two for the connection is the database name itself. I then tried changing the said config file so reflect the new database (which means I only changed the name of the database), and the error reappeared.
So here's what I have:
1) Permissions are exactly the same as old script is.
2) Files are exactly the same as old script files excluding the database name in the config file.
3) User is exactly the same as older database.
4) I'm able to access the older database from the same folder/file which the error is occurring merely by changing the database name.
5) I looked up the problem on the script forum and found that someone else's host had been the problem (see here)
6) With the database name set to the new database, I can change the password to ANY other word and it will see it as correct EXCEPT when I use the correct password.
7) The error message gives the first part of the user name (the portion before the underscore) but the second half is missing.
8) I tried changing the database name, but the error was still there.
9) I tried re-uploading the files for the script 4 times, but the error still showed up.
10) I manually uploaded the older database tables into a new database and successfully connected to them. The correct way, however, would be to allow the install file for the script to create the tables. I've read where some hosts are blocking the ability to use file names with the word "owned" in them (see here). I can't access a file with the name of owned.php in the admin panel and one of the table names for the database is named "owned."
So maybe the problem is HostGator is blocking the "owned" names through various means, thus interfering with both creation and use of the file/table with that specific name? Can anyone confirm this for me?
I've used the Enthusiast script for several years and can connect fine to the old database, but I've recently downloaded the script for a new site I'm working on.
I followed the steps accordingly and included the (nearly identical) database information into the configuration file. Now I'm getting this error:
Code:
Warning: mysql_connect() [function.mysql-connect]: Access denied for user 'animara'@'localhost' (using password: NO) in /home/user/public_html/website/admin/mod_owned.php on line 1711
Cannot connect to the database. Check your config file and try again. MySQL said: Can't connect to MySQL server onThen I tried transferring the files from the older script to the new folder/site. This was under the assumption the new downloaded script had an improper code somewhere. After the transfer I was able to access the old database from the new site.
To add, both the older database and the newer database for the scripts have the exact same user (and thus assumedly the same pw). The only difference between the two for the connection is the database name itself. I then tried changing the said config file so reflect the new database (which means I only changed the name of the database), and the error reappeared.
So here's what I have:
1) Permissions are exactly the same as old script is.
2) Files are exactly the same as old script files excluding the database name in the config file.
3) User is exactly the same as older database.
4) I'm able to access the older database from the same folder/file which the error is occurring merely by changing the database name.
5) I looked up the problem on the script forum and found that someone else's host had been the problem (see here)
6) With the database name set to the new database, I can change the password to ANY other word and it will see it as correct EXCEPT when I use the correct password.
7) The error message gives the first part of the user name (the portion before the underscore) but the second half is missing.
8) I tried changing the database name, but the error was still there.
9) I tried re-uploading the files for the script 4 times, but the error still showed up.
10) I manually uploaded the older database tables into a new database and successfully connected to them. The correct way, however, would be to allow the install file for the script to create the tables. I've read where some hosts are blocking the ability to use file names with the word "owned" in them (see here). I can't access a file with the name of owned.php in the admin panel and one of the table names for the database is named "owned."
So maybe the problem is HostGator is blocking the "owned" names through various means, thus interfering with both creation and use of the file/table with that specific name? Can anyone confirm this for me?