I am trying to: I made a CPT with a WYSIWYG field
Link to a page where the issue can be seen: hidden link
I expected to see: A white window where I can put some formatted text
Instead, I got: A greenish background. I can place text in it, but after updating CPT, the text is gone. The onlt way to get some text in the window is via the Text-window. Back in the Visual window I can not change a thing. That is: I can change, but after saving the changes are gone again.
Search some hours for an solution ;-(
Hello and thank you for contacting Toolset support.
We have currently an issue, with WYSIWYG fields, that affects only post types that have the "Editor" option disabled. As a workaround, I activated the "Editor" option in the post type. Check this screenshot hidden link
I'll keep you updated about this issue as soon as we have it fixed, so you can disable the "Editor" option.
Hello Jamal,
All clear, butt..
On the same site I also installed WPML and in the translate screen it's still the same. Is that the same issue?
Hope you can solve this quickly.
Regards,
Petran
Hello Petran,
Maybe it is also caused by the WP 5.8 update. I could not find any similar reports here on Toolset.com. I can't really confirm.
I added a WYSIWYG field to the default posts type, and in the translation editor, the visual tab is not working. But, the Text tab is working, and I am able to save.
Let's see if the developers fix the issue for the WYSIWYG field, and we'll check the issue with the translation editor.
Hello Jamal,
Hope to hear soon from you with good news 😉
Thanks so far.
Hello Jamal,
It looks it has to do with the choice of the content editor. Choosing Blocks is giving me problems. When I choose for classic, the WYSIWYG editor does work (although not in WPML). On wpml.wplabo.nl I changed the Blocks to the classis editor (of Posts) and that works fine.
Regards,
Petran
I'm still pushing the devs to try and fix this before the next round of plugin updates is released, which is expected soon (possibly next week).
It's not fixed yet, though, and we should know in the next few days whether a fix makes it into the upcoming releases.
Sorry for the delay.
