Clear your cookies, msbelle, and then log in again. Please advise if you get switched again.
Buffistas Building a Better Board
Do you have problems, concerns or recommendations about the technical side of the Phoenix? Air them here. Compliments also welcome.
have done it. will let you know if the board continues to hate me.
The board is loading reeeeeeeeeeeeallllllllllllllllly slooooooooooooowly for me this morning. Are we having problems?
No other Web sites (as of yet) are loading slowly, FTR.
It's working snappily for me.
There's bugs when someone tries to register with certain punctuation in their user name. Two things I've seen recently:
- An apostrophe -- The validation URL doesn't work. I'm sure there are other delimiting problems.
- A comma -- the confirmation email gets messed up as it gets divided into two addresses. For instance, if someone at email address joe@shmoe.com registers with the user name "Joe, Ruler of Shmoeville", the confirmation email address gets parsed as "Joe, Ruler of Shmoeville <joe@shmoe.com>", which incorrectly gets split into two addresses. It still works, but it's awkward.
We could try to patch each situation to avoid problems, or we could code to disallow certain punctuation in user names. I'd suggest the latter.
I like the latter too, Jon. I'll get on it.
How goes the prettification of the quote pages?
You mean the thing I completely forgot to do?
And perhaps not coincidentally, the thing I mostly forgot I ever mentioned.
I've been logged out repeatedly today. I am using Firefox on WinXP, and so far as I know, haven't changed any settings lately.
No changes had been made to the board code, so I'm not sure what could be making that happen -- is it possible you were switching from buffistas.org to www.buffistas.org or vice versa?
Speaking of logging, msbelle, I've found the core of your identity problem -- PHPSESSID. That's what PHP uses to track a user's settings if you aren't using cookies. It puts it into the URL. So if someone else uses a URL with your PHPSESSID, they become you for the duration.
I don't know if there's a way around it, programmatically, other than deleting that in the code from the URL if someone posts a local link. Which'll need to be tested.