Meta Box

WYSIWYG Editor Not Working Correctly

Support › General › WYSIWYG Editor Not Working CorrectlyResolved

Viewing 15 posts - 31 through 45 (of 49 total)
1 2 3 4
  • Author
    Posts
  • January 9, 2021 at 4:51 PM #23945
    Anh TranAnh Tran
    Keymaster

    Hey guys, I've complete the fix for the editor. Now you can try it here - just download it and overwrite the js/wysiwyg.js file in the plugin.

    What I've done:

    • Disable re-rendering for classic editors to avoid extra work as Teia reported.
    • Fix the default editor settings as JC reported.
    • Apply re-render after reorder editors, or groups that contain editors.
    • Remove the extra CSS of the editors to speedup rendering. It'll be a huge benefit if you have many editors on the page (such in cloneable groups). This fix requires updating the wysiwyg.php file as well.

    I also update the fix for validation, e.g. required rule now working for editors as well.

    I've tested with single field, inside cloneable groups and in blocks. Please help me to test with your cases and let me know if you find any bug.

    Thanks,
    Anh

    January 9, 2021 at 9:17 PM #23947
    JCJC
    Participant

    Thank you Anh,

    second fix works for me but now the first return key will be ignored in Visuell mode. I always have to type it a second time.

    Best,

    Jan

    January 9, 2021 at 10:05 PM #23948
    Teia Local StudioTeia Local Studio
    Participant

    Hej there!

    Updating only the .JS solved my problems with the editor rendering in classic mode!
    Thank you!

    However, updating the .PHP file brings also to me — as reported by JC — the strange bug on VISUAL text input —— the ENTER KEY must be pressed twice to create a paragraph (or CTRL+ENTER twice for line breaks).

    Always thank you, Ahn & Team!
    G.

    January 11, 2021 at 11:38 AM #23960
    Anh TranAnh Tran
    Keymaster

    Hey guys, I've fixed the bug. Hopefully that's the final fix. Please try again and let me know the result!

    January 11, 2021 at 3:59 PM #23967
    JCJC
    Participant

    Hi Anh,

    the fix works for me. Thanks again.

    Jan

    January 11, 2021 at 4:50 PM #23969
    SLG MarketingSLG Marketing
    Participant

    Hi Anh

    I've tested this morning with your latest commits of wysiwyg.php and wysiwyg.js, and they seem to be working fine. I've also dployed them to our development server which you still have access to if you need to test them yourself.

    When can we expect these fixes to be rolled out to a proper update?

    Thanks for your support on this.

    January 11, 2021 at 5:50 PM #23971
    Anh TranAnh Tran
    Keymaster

    Done! New version is available on the WordPress.org now.

    PS: Can you do me a favor adding a 5-star review on WordPress.org? Thanks in advanced!

    https://wordpress.org/support/plugin/meta-box/reviews/?filter=5

    January 11, 2021 at 6:10 PM #23972
    Teia Local StudioTeia Local Studio
    Participant

    It's all fixed for me too!
    Five stars are not enough, you and MB team deserves 10 stars, in gold!
    Thank you, Ahn!

    Giovani.

    January 16, 2021 at 12:13 AM #24048
    YardYard
    Participant

    Hi Anh,

    I've a similar problem, when I load the editor I can see the wysiwyg editor but the font-color is set to white? When I switch to the text-editor and back to the visual the iframe is still set to display:none; I use the latest version of the metabox plug-in (3.5.7) and WordPress 5.6

    After loading the editor: https://ibb.co/Wy3ykPk"
    After switch text back to visual: https://ibb.co/HCtWYDh

    Do you know what the problem is?

    January 17, 2021 at 2:44 PM #24070
    Anh TranAnh Tran
    Keymaster

    Can you post the code that registers the meta box?

    January 18, 2021 at 3:40 AM #24076
    GunvorGunvor
    Participant

    My problem from post 23787 has been solved! Thanks!

    January 18, 2021 at 2:47 PM #24083
    YardYard
    Participant

    Hi Anh,

    My company is using a framework similar to Laravel but extended with WordPress support. This is the code:

    Metabox::add('post_internal_information', [
            'title'      => __('Interne informatie', config('app.text_domain')),
            'post_types' => ['page', 'person', 'wip'],
            'context'    => 'normal',
            'priority'   => 'high',
            'fields'     => [
                [
                    'name'  => __('Titel', config('app.text_domain')),
                    'id'    => 'post_information_internal_title',
                    'type'  => 'text',
                ],
                [
                    'name'    => __('Interne informatie', config('app.text_domain')),
                    'id'      => 'post_information_internal',
                    'type'    => 'wysiwyg', // this is the metabox currently having the issue
                    'raw'     => true,
                    'desc'    => __('Hier kunt u informatie toevoegen die alleen voor intern gebruik bestemd is.', config('app.text_domain')),
                ],
            ],
        ]);
    January 26, 2021 at 4:47 PM #24185
    JCJC
    Participant

    Hi Anh,

    today, after an Update to Meta Box AIO (1.13.0), the problem appeared on another website I'm working on ... White Text in visual mode, can't edit content in visual mode.

    Jan

    January 27, 2021 at 7:04 PM #24201
    Teia Local StudioTeia Local Studio
    Participant

    Hi Anh,

    I updated to MB AIO 1.13.0 in my recent site (custom theme) and the problem DID NOT RETURN. Everything IS FINE for me. I think it could be interesting to report.

    Thanks always!
    G.

    January 29, 2021 at 3:16 PM #24241
    Yard DigitalYard Digital
    Participant

    The problem Jan (26-01-21) speaks about is still occurring for me as well. The need for a fix is urgent because our customers are using this field regularly.

  • Author
    Posts
Viewing 15 posts - 31 through 45 (of 49 total)
1 2 3 4
  • You must be logged in to reply to this topic.