Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)
  • Anybody found a solution for this? I just started having the same problem, right after I upgraded to 2.0.4.

    resiny, you’re correct about this being the command to call the WYSIWYG editor (TinyMCE). You’re also correct about your temporary fix: turning off the visual rich editor makes the message stop. The error comes back on when the visual rich editor is turned back on.

    I tried your suggestion about replacing the /wp-admin directory from scratch. Still no good. Tried overwriting the tinymce directory, along with the whole /wp-includes directory. Also ineffective.

    Also, the message persists whether or not I have plugins turned on.

    I’ve found several threads on the board describing this issue, but none of them seem to spell out a solution — or, at the very least, explain why this problem crops up.

    Suggestions?

    Thread Starter crunchable

    (@crunchable)

    I don’t plan to provide comments on pages at this point, but I’m saving your tip just in case.

    Thanks very much for your help!

    Thread Starter crunchable

    (@crunchable)

    Thanks! That seems to do the trick.

    Any chance that this solution might cause other problems in other parts of the site? Otherwise, this looks like it solves my problem.

    Thanks very much for your help!

Viewing 3 replies - 1 through 3 (of 3 total)