Preview in PM
Not sure, if there is something wrong:
I was sending a PM by using the preview a few times, and as I believe each of the previews was sent as a PM.
I could not send the final PM, because the limit of 4 PMs per hour was reached.
Re: Preview in PM
Reply #7 –
Bug can happen if you click preview more than once..
for reference: öäüß
result after preview: öäüÃ
Re: Preview in PM öäüß
Reply #8 –
Looks like the strings (body and subject) are not properly encoded before being sent to the server before the preview.
Re: Preview in PM
Reply #10 –
I fixed the preview in fcf89327935fb0031e291b6c20e8585bf0cdf81a
The problem with the special characters seems to be the result of the "usual" mixed status the AJAX calls are all around the code.
In these AJAX calls (PM previews and posts previews, plus few other places), the texts are converted to 8bit strings before being sent to the server. In 1.0, that string was somehow processed and returned properly to the client, now it is not and the characters result broken.
If I understand correctly the problem, I would be tempted to drop entirely the usage of php_to8bit from the codebase, but TBH it's something I'm a little worried about...
What do you think? Scrap during beta and if something is broken let's find a solution, or let's find a solution to the preview before facing the "real" issue?
Re: Preview in PM
Reply #11 –
Would you have to update all the xml to json ? I don't know if xml is going to handle all of utf8 stuff so I thought that was why the utf8_encode (on the js side via php_to8bit was done).
Anyway for a 1.1 I don't think we should be redoing that, IMO All of that was fine in 1.0 ... I do remember having to update things for some of the 4 byte utf8 items.