All I did is change the cookie name in the admin panel and now the forums are down and I am getting all kinds of errors?
After I pressed the save button, I got this
LainaaConnection Problems
Sorry, SMF was unable to connect to the database. This may be caused by the server being busy. Please try again later.
So i went to the portal page and I got this:
Lainaa
Warning: mysql_query(): supplied argument is not a valid MySQL-Link resource in /home/jbmaudio/public_html/forums/SMF/Sources/Subs.php on line 321
Warning: mysql_error(): supplied argument is not a valid MySQL-Link resource in /home/jbmaudio/public_html/forums/SMF/Sources/Errors.php on line 123
Warning: mysql_errno(): supplied argument is not a valid MySQL-Link resource in /home/jbmaudio/public_html/forums/SMF/Sources/Errors.php on line 124
the url address of the portal page is www.jbmaudio.net
the forum page is www.jbmaudio.net/SMF/index.php
any help is appreciated
Can anyone help?
Changing a cookie name shouldn't cause the forum to go down. Are you sure you didn't change any of the database settings?
It looks ok now. Is this issue resolved? If so, did you use repair_settings.php to fix the problem or even edit the Settings.php file manually.
Some how the database password changed in the settings php when i changed the cookie name. i manually entered the correct password and it seems to be working.
I still get emails about once a week that say "could not connect to the database" though.
Who is your host?
As for the db password changing, firefox will sometimes love to do this if you have saved passwords enabled and you have one saved for your site.
Bluehost is my host
this is error I get about 2 times a week:
Lainaa
[email protected] to jbm
show details 7:30 PM (14 hours ago)
Reply
There has been a problem with the database!
This is a notice email to let you know that SMF could not connect to the database, contact your host if this continues.
As the message says, contact your host. It means that SMF could not establish a connection. Either the server was too busy and refused it, or the mysql server was not running, or it could have timed out during a connect.
I never had this issue when I was running supermod (that i knew of at least) that is why i bring it up.