CAN'T SUBMIT AN ARTICLE

Posts

Pages: first prev 12 last
Awh, no, not the FireFox bashing!!!
I've never had any issues like that with it, but I STILL use mostly IE only cause FF takes forever to load.
author=Enker link=topic=301.msg4043#msg4043 date=1192217852
Collander?
Sorry. I'm using my collander for my Cerebral Enhance-O-Tron.
author=Valentine link=topic=301.msg4124#msg4124 date=1192491821
Awh, no, not the FireFox bashing!!!
I've never had any issues like that with it, but I STILL use mostly IE only cause FF takes forever to load.

It's not like there is anything wrong with fire fox, it is just that Opera is a more reliable and safer program to use.
Interesting - is there a word limit for the blogs on the games pages? When I posted the promised Shadow's Reach walkthrough to accompany the demo (and let people see if they managed to find everything it has to offer) I got the following message:

UnicodeEncodeError at /panel/games/239/add_log_entry/
'latin-1' codec can't encode character u'\u2019' in position 474: ordinal not in range(256)
Request Method: POST
Request URL: http://www.rpgmaker.net/panel/games/239/add_log_entry/
Exception Type: UnicodeEncodeError
Exception Value: 'latin-1' codec can't encode character u'\u2019' in position 474: ordinal not in range(256)
Exception Location: /usr/lib64/python2.4/site-packages/MySQLdb/connections.py in defaulterrorhandler, line 33
http://www.rpgmaker.net/forums/index.php?topic=105.0 shadowtext removed some special characters.

As far as I can tell, latin-1 u2019 is the single backquote character. What a crazy character!
of course, now the article I submitted won't work...

I found this while looking for an answer:
Le samedi 04 novembre 2006 14:19,
qomics-iEnYTmFlAeCsTnJN9+BGXg@xxxxxxxxxxxxxxxx a écrit :
> UnicodeEncodeError: 'latin-1' codec can't encode character u'\u2019' in
> position 12: ordinal not in range(256)

C'est un problème de charset sur la base de donnée (elle reçoit un caractère
qu'elle ne peut pas encoder). Il faut que tu arrives à dire à mysql de bosser
en utf-8 pour cette base de donnée...
Le plus simple est d'avoir mysql >= 4.1, car il me semble que django le met
automatiquement en utf-8, et il me semble aussi que les versions antérieurs
ne supportent carrement pas l'utf-8 (mais ca je suis pas sur)
Essaye d'aller avec phpmyadmin sur ta base mysql et regarde si tu peux changer
quelque part le charset (ou interclassement) des tables de la base de donnée
qomics.

Si ca ne règle rien, il te faudra attendre que je teste de moi coté :)

Merci,

Panard


Got that, WIP?

(copy of error: http://www.sfu.ca/~kentona/UnicodeEncodeError_at_submit_article_.htm)
WIP
I'm not comfortable with any idea that can't be expressed in the form of men's jewelry
11363
I've actually dealt with something that might be related to this, at work. I'll see if I can't find some time to look into it more.
FYI, for anyone who cares, characters that give difficulty are the back-apostrophe (`) and double spaces ( ). Avoid those when submitting articles and reviews until WIP fixes the bug.

If you get that crazy error message, copy the contents section and look for the \xe2 \x80 \x99 characters. That's the characters giving you trouble - take them out of your original article and try again.
Pages: first prev 12 last