Custom Fields
Support General Bug with WYSIWYG on non gutenberg post

  • Creator
  • #28240
    Mr Jon Marks

    If when a page loads a user starts on the text tab of a WYSIWYG (either the post content or a meta box) and clicks the visual tab - although the UI looks to have changed - the content still reads from the text tab.

    This means clicking the text tab does nothing as it thinks it is on that tab already.
    Entering any content in the visual tab does not save - as the saved value is taken from the text tab.

    Clicking the visual tab a second time loads the tab properly.

    This is a classic editor post (regards less of if the post type supports the body), Metabox 5.4, WordPress 5.7 and a clean install with no other plugins.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Author
  • #28241
    Mr Jon Marks

    Not the normal post content WYSIWYG work fine on classic editor, but if you add a meta box WYSIWYG to the post type the normal one then breaks.

    I am guessing you have a hook that requires some JS that is only in the Gutenberg view. There are no console errors.

    Long Nguyen

    Hi Jon,

    Thank you for your feedback.

    I've informed the development team to check this case. I will get back to you if there is any information.

Viewing 2 replies - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.