I am trying to:
Add content to a custom field WYSIWYG
Link to a page where the issue can be seen:
hidden link
I expected to see:
An editable field.
Instead, I got:
A field that cannot be edited.
Additional info:
I've tried deactivating all other plugins and switching the theme. Not seeing anything in the error log. This is a recent issue.
To add more info, it seems that this issue only happens in Firefox.
Hi, I'm checking this now. I may need to "take over" editing of this page for a moment in wp-admin.
Sure, feel free. I just forgot to close the tab, go ahead and take over the post.
Thank you, I'm finished testing on your site and you can take over as needed. After running some more tests locally, I was able to replicate this issue on my own local test site. It seems to be specific to Firefox, as you mentioned, and it is also a bit sporadic. I'm not 100% sure of the circumstances yet, but it seems to be dependent somewhat upon when the post was created and/or the contents of the WYSIWYG field. Sometimes when editing older posts with contents in the WYSIWYG field, the Visual editor seems to work as expected. Sometimes newer posts with no content in the WYSIWYG field seem to be broken...regardless, it's an issue that our 2nd tier team needs to investigate in more detail. I'll escalate the issue and keep you posted here as I receive more information.
Our 2nd tier support team has escalated this issue to our developers, and I'll continue to update you here as I receive more information.
Our developers have informed me that there is an open issue in WordPress core related to this: https://core.trac.wordpress.org/ticket/52133
We expect this issue must be resolved before the Visual tab is working correctly, and I'll let you know as I receive more information about this problem.
Just a quick update to let you know we are still waiting on the core WP problem resolution on this.
You can follow along in our erratum post here: https://toolset.com/errata/visual-tab-of-wysiwyg-field-doesnt-work-in-firefox/
Hello, I can see there has been some progress on the WP core ticket here: https://core.trac.wordpress.org/ticket/52133
The relevant ticket has been updated and marked as "closed", stating that the issue will be resolved in the upcoming WP 5.8 release. I will make an internal note here to loop back around to this ticket for confirmation once WP 5.8 is released.
This issue should be resolved in the latest WordPress release.
