I upgraded my servers PHP from 5.2 to 5.4 and now I get the error: "Script Error Error establishing a database connection. Please contact site webmaster if this error does not disappear long time" My hosting support wasn't much help and neither was this forum. What's the simple answer?
Try updating your database passwords. Think the problem may be PHP 5.4 can't handle database passwords created pre mySQL 4.1 This might help http://community.webfaction.com/que...ress-error-establishing-a-database-connection You might have to create a new user for the databases and then change the Wordpress one to reflect new user
I upgraded to 5.3.28 instead and did not get the database error...however, now I get the following when trying to add a new member.... DateTime::__construct() [<a href='datetime.--construct'>datetime.--construct</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CST/-6.0/no DST' instead
I tried adding " date_default_timezone_set('America/Chicago'); " to my config.php file as suggested in another topic, but still having the same issue. Nobody can signup now.
So now not even my paid members can log in. Wow, I'm absolutely amazed at how 4.3.5 seem to be incompatible with PHP 5.3.8 or higher.
It may actually be that Joomla version 1.5.26 is NOT fully compatible with PHP 5.3.28. http://forum.joomla.org/viewtopic.php?p=2156832 If anyone else out there is running these versions successfully, please let us know.
Oh, and the time issue was solved by modifying PHP.ini "date.timezone" parameter from "CST" to "America/Chicago", makes a difference I guess.
Rolling back to PHP 5.2.17 and now everything works fine again. Support told me that it "impossible for PHP 5.3.28 to break single login function" of the Joomla plugin. Apache is at ver 2.4. Will file a detailed bug report.
Why not try suggestion above????? This is NOT reallt an aMember problem research has revealed it is a changes with PHP so why continually blame aMember??