AdvancedCustomFields / AdvancedCustomFields/acf
Wordpress 5.6 - WYSIWG Fields
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 945
- Forks
- 197
- PR merge metrics
- No merged PRs in 30d
Description
I've just updated to Wordpress 5.6 and noticed that now wysiwyg-fields I've used on pages and posts stopped working. That is only the case for pages and posts using the Gutenberg editor. I tried deactivating all other plugins which had no effect.
The wysiwyg-field is visible and the text mode can be used normally. However the visual mode is just plain white and doesn't show any text. I've noticed, that the text mode now shows p-tags, which haven't been there before. Once I remove them I can see my text in the visual mode too. That text disappears as soon as I hit save again and the p-tags are back in text mode.
Is there any solution to this problem?
ACF Version 5.9.3
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue with WordPress 5.6, Gutenberg, and ACF 5.9.3 using a page or post with a WYSIWYG field; compare the text and visual modes before and after saving. No source file or test is named in the report, so first locate the Gutenberg WYSIWYG integration and its existing tests; done means saved content remains visible in visual mode without unwanted p-tags.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, wordpress
- Domain
- content
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100