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:
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.
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.
Updating only the .JS solved my problems with the editor rendering in classic mode!
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!
Hey guys, I've fixed the bug. Hopefully that's the final fix. Please try again and let me know the result!
the fix works for me. Thanks again.
I've tested this morning with your latest commits of
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.
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!
It's all fixed for me too!
Five stars are not enough, you and MB team deserves 10 stars, in gold!
Thank you, Ahn!
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?
Can you post the code that registers the meta box?
My problem from post 23787 has been solved! Thanks!
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')), ], ], ]);
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.
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.
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.