Sauf erreur, tu as dernièrement installé l'éditeur fckeditor et lasco t'as donné un lien pour télécharger la dernière version.
En allant regarder sur le site proposé par lasco, j'ai vu qu'il y avait un problème avec les caractères spéciaux
Citation :HTML Special Characters Issue For whatever reason, this error still persists — even in the XOOPS 2.3.3 release of FCKeditor 2.6.3. XoopsEditor 1.21 solved it by getting rid of the undoHtmlSpecialChars call in formfckeditor.php (as introduced in the XoopsEditor 1.10 release). However, it was re-introduced. I expect there is a reason that this call is made by FCKeditor for some sort of protection in case someone adds a special character in the source side - ::shrug:: This fix applies to FCKeditor 2.6.3 as released in XOOPS 2.3.3. Using any special characters cause an unintended cascading effect of ampersand conversion. For instance, a quote " will become " in the code — as it should be. However, after FCKeditor retrieves it from the database and displays it, it becomes " in the WYSIWYG instead of ". The next time it becomes " and then " ad infinitum. What I had to do was change fckeditor_php4.php and fckeditor_php5.php, approximately line 158 to (in function CreateHtml): // $HtmlValue = htmlspecialchars( $this->Value ) ; $myts =& MyTextSanitizer::getInstance(); $HtmlValue = $myts->htmlSpecialChars( $this->Value ) ; This is because this XOOPS implementation uses the $myts->undoHtmlSpecialChars function before throwing it back into the database so we need to use the XOOPS version of the htmlspecialchars function.
Bon, je ne suis pas très fort en anglais mais je crois comprendre qu'il faut modifier quelques lignes dans quelques fichiers.
Maintenant, reste à savoir si ces problèmes de caractères spéciaux sont liés uniquement à fckeditor avec Xoops 2.3.3
Peux-tu tester ?