errors with the rich text editor in Firefox/IE

• 

  arturogoga · Member · Jan 6, 2006 at 6:04 pm

  • Copy link
  • Add topic to favorites

  Whenever I try to use the rich text editor in WordPress with Firefox/IE/Opera, while it is loading the page, it directs itself, for some reason, to:

  http://arturogoga.wordpress.com/wp-admin/wpmu-feedback.php

  And when I hit back, it just does the same again, thus not allowing me to use the editor. Is this a known bug, or something?

• 

  matt · Staff · Jan 6, 2006 at 6:13 pm

  • Copy link

  Never heard of this.

• 

  arturogoga · Member · Jan 7, 2006 at 1:54 am

  • Copy link

  It happens in Opera too, by the way. But after hitting back, it stops.

• 

  arturogoga · Member · Jan 7, 2006 at 3:51 pm

  • Copy link

  Am i the only one with the problem? The weird thing is, is that it happens in all the browsers, and with the rich text editor only.

• 

  matt · Staff · Jan 7, 2006 at 9:06 pm

  • Copy link

  Maybe you have some sort of other program modifying the javascript, like Norton or something.

• 

  arturogoga · Member · Jan 9, 2006 at 4:53 am

  • Copy link

  here’s a screenshot of the javascript errors I get in Firefox:

  

• 

  arturogoga · Member · Jan 9, 2006 at 4:55 am

  • Copy link

  and another one
  

• 

  cgsprite · Member · Apr 10, 2006 at 2:45 pm

  • Copy link

  Well my rich text editor has gone walk-about, its totally missing, it was working last week, but since its been coming and going. :( duno what to do.

• 

  drmike · Member · Apr 10, 2006 at 6:25 pm

  • Copy link

  Turn it off and use the normal editor. You’ll have better control over your text and code anyway.

• 

  betterdays · Member · Apr 10, 2006 at 10:19 pm

  • Copy link

  I’m having the same problem as cgsprite–the rich text editor is just gone

• 

  kfsone · Member · Apr 10, 2006 at 11:29 pm

  • Copy link

  Seems to be two problems at play here:

  1/ IE doesn’t like the attempt to fetch http://google-analytics.com/urchin.js from within a https:// page.

  2/ The various scripts within the page do not always load in the same order. This could be fixed by using the defer=”defer” tag judiciously to ensure that the browser doesn’t start trying to execute dependent code until all loading is done.