UBB.threads PHP Forum Software Community Forums UBB.threads 7 Bug Reports Fixed Bugs [FIXED for 7.2] Error PM'ing a user with "special characters" in their name.

I have a user on my forums named "§intå×" (which is my co-admin, which can be an issue); as of installing 7.1 I am unable to PM them. With 7.0.2 I could message them without issue.

I'm unsure if this is just PM's at this time, as I JUST noticed it...

Do I see a 7.1.1 in the near future?

I don't think we've ever had a feature release that wasn't followed up by a bug fix release at some point Somethings will always slip through.

Yeh, just kinda sucks that I cna't message my coadmin :x

I bet he's made up (Kidding) lol

Is that happening only in the display name?

The javascript is probably barfing on the special characters. It doesn't like them very much and always extra hoops to go through that I'll need to figure out.

What all changed on it since 7.0.2? It worked fine then

It was broken in 7.0.2. Remember the bug reports concerning sending private messages? Those were because a couple of the javascript functions weren't being called. Now that they are being called properly, the special characters are causing an issue. Not sure on the fix just yet.

lol, well, they may have been "broken" in 7.0.2 but i was able to pm him without issue until i upgraded from 7.0.2 to 7.1 ... Go fig, fixing one issue b0rks another haha...

Gizmo, you may try changing your language encoding to UTF-8 in the language file. Making this change allowed me to PM users with those types of characters. Not sure of another fix yet, but still testing.

Lol now the users username shows up as blocks with qquestionmarks and theres no way to update their display name (as the controlpaneldoesn't use the UTF-8 setting

ok, i 'became this user' and updated their display name, and was able to send them a pm with their special characters...

lol this user in the cp now looks like:

Blah, ok. So the name is probably encoded in the db with another format. I really need to bite the bullet in an upcoming release and just switch everything to UTF8 and then have the upgrader convert the old content as well. Maybe convert all of the time formats to UTC at the same time. Just don't want to have to put out such a major upgrade just yet

Will see if I can find some other fix for this now.

lol, why UTC? I like using the unix epoch

I'm talking about the base timestamp. They will still be stored in unix epoch, but right now they are stored with the adjustment of the server time offset. So, that leads to varying time problems like the one just noted when we switched to daylight savings time

Ahhh, so long as they're stored in unix time I can live with any change... lol...

On all of my scripts I use set-env to set the default timezone to GMT then do the time procesing live; for offsets as well, and daylight savings time, just all the if/else can get kida bulky lol

This seems to be unfixed in 7.1.1, right?

the fix is the UTF-8 characterset, which renders extended characters as odd characters without converting; so it will remain unfixed until Rick can find a way to convert previous posts in the database at once.

Yeah, as Gizmo stated, this one is currently unfixed. I think I may just go the route of changing the Private Message ajax over to plaintext instead of xml like we do for the preview. Switching the databaes contents to utf-8 is a pretty big leap that I'm not too sure we want to do just yet.

Hey, so long as it works I'm sure we'll all be happy lol

Are there special considirations when I update the display name column to utf8?

Do I change it to uft8-bin or utf8-general? Or doesn't it matter?

utf8-general should be what you need. I'm saying should here because I'm not positively sure.

I simply changed my forum characterset to UTF-8 vs updating the sql db