Meta Box

Content Editor Visual Editor Selection

Support › MB Frontend Submission › Content Editor Visual Editor Selection

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • March 12, 2023 at 1:00 AM #40961
    Jean Pierre FrancoisJean Pierre Francois
    Participant

    Hello,

    Our frontend users will be mainly customers who don't have the required knowledge for code editing etc.

    As such, based on this screenshot https://tinyurl.com/2qms9qlu

    - I would like to disable the text editor and only make the visual editor available by default.

    I tried using some CSS code to hide the "Text" tab but then on reload, the "Text" tab doesn't show up which is good but it is still showing the "Text" editor instead of the visual editor.

    So, my objective here is to completely disable the "Text" editor on the frontend submission form and make the "Visual Editor" available by default to all frontend users.

    March 12, 2023 at 3:00 PM #40969
    PeterPeter
    Moderator

    Hello Jean,

    You can set the editor option quicktags to false to remove the Text tab in the WYSIWYG field. If you are using the Meta Box builder, please check this screenshot https://monosnap.com/file/fYqCyD7ERGP6FZG6HC7ve6VFpP1ben

    and read more on the documentation https://docs.metabox.io/fields/wysiwyg/#settings

    March 14, 2023 at 11:53 AM #40999
    Jean Pierre FrancoisJean Pierre Francois
    Participant

    Hello, this is the post type content editor, this is not a WYSIWYG custom field editor, how can I access the default content editor to make this change?

    March 14, 2023 at 5:36 PM #41000
    PeterPeter
    Moderator

    Hello,

    Does that mean you are using the plugin Classic Editor? If yes, please contact the plugin support to get further assistance. Or follow this topic to use the custom code https://wordpress.stackexchange.com/questions/174079/remove-quicktag-buttons-but-not-visual-text-editor-and-tabs

  • Author
    Posts
Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.