Looks like just you and Fred Pete got that error, DX. Let's hope it was a twitch, but tomorrow I'll go over the logs and see what was going on at 8:17.
I changed the code to strip tags from the t title tag.
Do you have problems, concerns or recommendations about the technical side of the Phoenix? Air them here. Compliments also welcome.
Looks like just you and Fred Pete got that error, DX. Let's hope it was a twitch, but tomorrow I'll go over the logs and see what was going on at 8:17.
I changed the code to strip tags from the t title tag.
Looks like just you and Fred Pete got that error, DX. Let's hope it was a twitch, but tomorrow I'll go over the logs and see what was going on at 8:17.
Yeah, it was just the one time, and I've been sailing along since. Shrug.
Just now, where the thread (or Message Center) should have been:
October 15, 2003, 12:05 pm Jess PMoon[20]: ERROR [2] mysql_connect(): User bufforg_phoenix has already more than 'max_user_connections' active connections line 78 of file /home/bufforg/public_html/classes/giles.php
There has been an error. It's of the type we call fatal. Please don't be scared. You're not the one that's going to die.
Okay, where the $$&#&(@#& are the developers?
Got the same thing just now:
October 15, 2003, 12:09 pm Aimée[68]: ERROR [2] mysql_connect(): User bufforg_phoenix has already more than 'max_user_connections' active connections line 78 of file /home/bufforg/public_html/classes/giles.php
There has been an error. It's of the type we call fatal. Please don't be scared. You're not the one that's going to die.
Okay, where the $$&#&(@#& are the developers?
Me as well:
October 15, 2003, 12:09 pm tina f.[953]: ERROR [2] mysql_connect(): User bufforg_phoenix has already more than 'max_user_connections' active connections line 78 of file/home/bufforg/public_html/classes/giles.php There has been an error. It's of the type we call fatal. Please don't be scared. You're not the one that's going to die.
Okay, where the $$&#&(@#& are the developers?
Me too, about three times in the space of two minutes.
Got the message too, but seem to be OK now.
Huh. I have yet to hit any kind of a hiccup today.
Which, of course, means that, now that I've said that here, I'll be getting all the bad error messages as soon as I hit "Post Message."
I just got that same error too, coming back after a threadsuck. But now, okay.
Just got it reading Buffistechnology.