While I hate to rule anything out, I can say with confidence that the thread title is not not cause of the wonkiness.

ita, I bet Tom would love to see the output from that MySQL status script I gave you the other day.

Cindy, I meant when ita changed the coding for the Title Bar, which involved changing the code for the page. The other changes, that happened earlier, had to do with the format we followed in entering a particular piece of data, i.e., the title for Natter 17.

Cindy, I meant when ita changed the coding for the Title Bar, which involved changing the code for the page. The other changes, that happened earlier had to do with the format we followed in entering a particular piece of data, i.e., the title for Natter 17.

Thanks, DX. Sorry for the slowness. Okay, well, it was just a stab in the dark. The thread header stuff was the only change (and different than usual kind of change) I could think of. I don't know how it works, so I didn't know if by using htmlified font and funky characters in the title, it was causing some other connection to be opened, or something.

I don't know how it works, so I didn't know if by using htmlified font and funky characters in the title, it was causing some other connection to be opened, or something.

The title, as stored in the database, doesn't actually contain the special characters, only the codes for the special characters. The translation doesn't actually occur until it reaches the browser window, so it's hard to see how it could be causing connection errors.

(The problems we had when we opened the thread were sort of the result of this. When I went to open the previously created thread, the maintain threads page translated the codes to the special characters, then when I unchecked the "closed" flag to open the thread and hit submit, the page submitted the special characters as the revised title data, with hilarity ensuing until Jon went in and fixed it.)

Tom, I've sent you some medium incomprehensible db_status pages -- a couple from September, and a couple from last week.

I've also rolled back the code to the "displays funny title bar" version, FWIW.

I've also rolled back the code to the "displays funny title bar" version, FWIW.

Still getting the error message, post-change.

Still getting the error message, post-change.

Me, too. What if we changed it to the stapler-looking pi, or just wrote "cos(pi)"?

I know my stab makes no sense. I understand what DX is saying. It's just that's the differentish Natter title is the only difference between when things did work, and now. Wouldn't an outside attack/spider/whatever would have ended by now? The host says there's been no change. We've made no change. Our volume wasn't particularly high when the errors started up.

Could it be the Dark Lord Sauron?

Just got this message now:

October 20, 2003, 9:06 am JohnSweden[973]: 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?

Cindy -- We had the problem last month before the new natter title. That time, the problem fixed itself. It's not the Natter title. Really.

However, I cannot rule out the Dark Lord.