Tiny MCE

  • Resolved baregrass

    (@baregrass)


    16 years, 2 months ago

    Since upgrading to 2.7 my tinymce is acting strange in wysiwyg mode, html mode works fine. The problem is that as I run across the top control buttons in visual mode all works well up to and including the unlink command button. The page break, spelling, full screen and color picker buttons will not work. As well, the right 1/4 of the edit screen is non responsive as well. I can’t put a cursor there but can insert a cursor in the left 3/4 of the screen. Seems like a javascript problem but where do I start looking? If anyone can help I would really appreciate it.

Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter baregrass

    (@baregrass)

    Additional info:
    I deleted and reinstalled my wp_admin and wp_includes folders to no avail. I’ll try and track down javascript errors and post them here.

    Thread Starter baregrass

    (@baregrass)

    I installed tinymce-advanced.3.2. It went a long way towards solving my problem.

    Thread Starter baregrass

    (@baregrass)

    Problem back again even with tinymce-advanced.3.2. It is really aggravating. Does anyone have a solution?? I mean I can do my posts up on NotePad using html and paste them into the html edit screen but why have a visual editor if I have to do that?

    Thanks

    it would be useful to know what browser you are using, and whether or not you have tested the same fucntionality in other browsers, and what those results were.

    Thread Starter baregrass

    (@baregrass)

    Whooami, Thanks so much for the answer. I think I have solved the problem. As I mentioned earlier the problem started when I upgraded to 2.7 and I was leaving the publish and category tabs on the right side of the editor. I finally figured out, this morning, that the editor was impinging on the space that those tabs required therefore rendering inoperable the right side of the editor. When I discovered this I moved the tabs under the editor allowing the editor screen to expand and all is working well at this point. Such a simple fix and so elusive for a long time! I feel foolish that I didn’t catch it sooner. Hopefully this will help any one else that has the same problem.

    Many thanks, baregrass! That solved MY problem, too. In response to Whooami, it was a cross-browser issue for me. I regularly use Google Chrome, Opera, FF, Safari, K-Meleon and (when I have to) IE. It was a problem in ALL of them.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Tiny MCE’ is closed to new replies.