Fork me on GitHub

Rapport de message :*
 

Re: Xoops 2.4.3 et codes UTF numériques

Titre du sujet : Re: Xoops 2.4.3 et codes UTF numériques
par trabis sur 05/01/2010 14:34:45

Citation :

kris a écrit:
Ensuite concernant le core, pourquoi ré-encoder ce qui est déjà encodé ?


If I write & a m p ; why should core automatically convert it to an & before aplying htmlspecialchars? Why does not core assume that I want to output it has I wrote it? That is(one of the reasons) why we allways had problems with the code box.

In 2.4.3 all modules/core that introduce encoded characteres in database will output double encoded characteres, meaning that they will output just like they are in the database. An example is the shoutbox module, but this can be fixed easily in the module.

The current french translation works fine for direct output but not when values have to be inserted into the database. In the profile example, we would have to use $myts->undoHtmlSpecialChars($encoded_language_string) before saving values to database but I don't think that would be good solution.

Has I said in other post, I consider this to be a long date bug in xoops, maybe since day one. We can expect some modules to produce undesired output but they should very few and easy to fix.
Propulsé avec XOOPS | Graphisme adapté par Tatane, Grosdunord, Montuy337513

72 Personne(s) en ligne (58 Personne(s) connectée(s) sur Forum) | Utilisateur(s): 0 | Invité(s): 72 | Plus ...