Problem with WYSIWYG an internet explorer 7

tk421 · Post by **tk421** » Wed Jan 03, 2007 8:40 pm

I've got a problem with WYSIWYG editor. It does not appear in Internet Explorer 7, but yes in Firefox.

Anybody knows if there is any problem with WYSIWYG and IExplorer 7?

tk421 · Post by **tk421** » Wed Jan 03, 2007 8:43 pm

I've found the next javascript error when the page is tryng to load WYSIWYG (i think). The error is:

HTMLArea.I18N.tooltips is null or is not an object

I have reviewed this topic (http://board.s9y.org/viewtopic.php?t=77 ... ltips+null) but the error stills.

The error is only in Internet Explorer both 6 and 7, but not in Firefox.

Any idea?

Post by **garvinhicking** » Thu Jan 04, 2007 3:13 pm

Hi!

Which language and which charset are you using for s9y? Does it also happen when you use english as language?

Best regards,
Garvin

tk421 · Post by **tk421** » Thu Jan 04, 2007 5:47 pm

The language is Spanish and the charset is native. I've also tried the UTF-8 charset but the error stills.

If i change the language to english the WISIWYG runs ok, but i want it to run in spanish.

There is any way to solve the problem?

Thanks

Post by **garvinhicking** » Thu Jan 04, 2007 8:50 pm

Hi!

Which serendipity version are you using exactly? It is a problem in the language file of the WYSIWYG editor (in htmlarea/lang/es*.*)...

Best regards,
Garvin

tk421 · Post by **tk421** » Fri Jan 05, 2007 11:41 am

I upgraded to version 1.1 two days ago, but i've reuploaded again the complete htmlarea directory today, and the error stills.

Any other idea?

Post by **garvinhicking** » Fri Jan 05, 2007 1:02 pm

Hi!

Could you temporarily delete the "htmlaarea/lang/es.js" and "htmlaarea/lang/es-utf.js" files and then copy "en.js" to "es.js" and "en.js" to "es-utf.js"?

I believe that the spanish files might contain special characters that disturb the IE. Sadly I can'T read spanish so I don't know if there's any special character that's causing the problem in this file...

Regards,
Garvin

tk421 · Post by **tk421** » Fri Jan 05, 2007 5:46 pm

Thanks garvinhicking, it worked. May be a failure caused by some special spanish characters like "ñ".

If I have a few of time i'll try to solve the problem editing the spanish js files.

Thanks again.

Post by **garvinhicking** » Sat Jan 06, 2007 12:49 pm

Hi!

Would be great if you could find out which character(s) cause the problem! Have fun!

Regards,
Garvin