WordPress.org

Ready to get started?Download WordPress

Forums

Problem with TinyMCE comment plugin after update (3 posts)

  1. S.W.Anderson
    Member
    Posted 5 years ago #

    Updated to WP 2.8 last night with no apparent problem. Everything was where it should be and all the plugins worked.

    Early this afternoon, the instant updater plugin and TinyMCE Comments plugin both updated. That's when the trouble started.

    In Firefox 3.0.11, the form frame for comments is only visible for a fraction of a second when the page first draws. TinyMCE's editing tools are nowhere to be found. The following text string appears within the comment form, but only for a fraction of a second:

    <p><br mce_bogus="1"></p>

    In Internet Explorer 7, the TinyMCE comments form frame renders OK, but that spurious text string is there.

    It is possible to enter a comment, although few if any visitors would know where and how without seeing the form to work in. So, I have deactivated TinyMCE Comments. I left a message at the plugin author's Web site, but noticed a request there to mention any problems with the update here.

    I tried deactivating Spam Karma 2, the Ajax Comments plugin and several other things, one by one, to see if doing so would resolve the problem. Nothing at my end changes or resolves the problem.

    I hope someone here or the TinyMCE Comments author will be able to fix the plugin.

  2. S.W.Anderson
    Member
    Posted 5 years ago #

    Problem solved. I uninstalled latest versuion of TinyMCE Comments and reinstalled previous version. Voila! Eveything works.

  3. beanmg
    Member
    Posted 5 years ago #

    TinyMCE missing WYSIWYG buttons

    I have been following many threads on the loss of editing buttons in the visual mode of tinyMCE Advance under WordPress 2.8

    My 'cure' concerns faulty PHP coding in one of the new (for 2.8) modules: wp-includes/js/tinymce/tiny_mce_config.php.

    In my copy - installed automatically - and also in a fresh copy of 2.8 that I downloaded today (19/06/09) the <?PHP coding is not closed with a ?>

    Adding the ?> my visual editor shows the edit buttons correctly.

    I guess browser differences reflect the differnt ways each handle error conditions.

Topic Closed

This topic has been closed to new replies.

About this Topic