#1 Yeah, that's certainly annoying. The backslash issue has been around for several years now, but the quote problem is still relatively new. Either one makes editing a post or especially a Resource a pita!

It's way past time that either one was fixed.

#2 I was so frustrated last night as I spent more time fixing my post to get it to look right than I did writing the code. It tends to deincentivize sharing code.

I have used lots of CMS frameworks and I have never seen anything like that before. Is it some custom PHP or something? It is easy to reproduce so we have that going for us. That should make it easier to isolate.

The one that worries me is the slash. It seems to trigger an escape sequence. This might be used to do something nefarious like a buffer overflow of the webserver.

#3 The only official comment I've seen regarding either one is that it's a known issue and has been brought to the attention of the webteam... but apparently there's so much custom code to their webpage that's it hard to fix.

But yeah, you're right about it causing us to lose incentive to share code. I've got several Resource I've simply never bothered with simply because of the amount of work it would take to correct if I ever edited them.

#4 Okay, I finally broke down and fixed this partially:
www.garagegames.com/community/resources/view/21864

The slash issue I can live with as it is not an easy fix to isolate. I don't really do escape characters in code very often.

#5 GG: Mail me if you need somebody to look at the frickin' UTF/I18N issues. It's alright to admit if you're struggling. This shouldn't be rocket surgery, though. My own PHP crap supports even Irish names without freaking out! (And I need it, with the co-admin being Irish.)

Is Zend really so limited you have to code input/output yourselves?

#6 This is a problem that stems from many iterations of the site. We haven't updated any posting code in a long time. However, there has been some admin panel data entry code that has been updated. Much of it uses the old, old, old GG site codebase. We're looking back through the repo commits to see where this change could have been made in the last several months.

#7 I don't know how your system is structured, but the Javascript code I wrote could solve the & issue by being applied after everything else has. Most sites have a Javascript function that runs after everything is loaded to clean up, fix, rearrange, etc. The function could go in there for GG. It only looks at the content box for forum submissions.

Yes, it is a hack, but since this site is going to be updated it saves you time and saves everyone posting a LOT of frustration.

#8 It should be fixed now.

#9 "Are you """sure""" about that"?

& also ' ; : do these things work?#~

[edit]

HUZZAR

My Face When:

Dave MB for Prez! Yeah I know he's only the messenger but hey :P

[double edit]
And I've edited again! And it still works!

#10 They should.

#11 Okay, backslash is still bust but if it's just that, we can live with it.

#12 Upon editing a resource all my quotes(") are being replaced with &quote; and & with & in the text area box. Definitely not fixed.

#13 Do you get it with blog posts as well so I can have the webteam and QA go through these areas?

#14 Resources are still bust and so are blogs. Just forums fixed. My ecstatically happy little girl gif was too soon ...

#15 Alright, I have tested and confirmed that the &(ampersand) and "(quote) problem has been fixed on editing forum posts. But the problems still persist with blogs and resources, because presumably they're apart of different PHP code from regular forums that they haven't been updated yet.

Now the only part that needs to be fixed is the backward slash disappearing issue and then we'll have a completely working forum. Yay! :D

#16 Plus PMs and hiding our e-mail addresses. And THEN it will be complete, apart from international issues, special symbols they didn't think of etc. But THEN it will be completely fine! Maybe.

#17 Blog and Resource body is fixed. I have tested editing the bodies of these, but the preview area is still a problem (the blurb you see when on the blog page).

#18 Or at least I couldn't get the body to break when I tested it.

#19 To do PM's right, we would want to move to a different forum system. As for e-mails, I'm not seeing them when I look at your profile unless I'm logged in as an admin.

#20 That's because I switched it off ;)