AdvancedCustomFields / AdvancedCustomFields/acf
WYSIWYG editor breaks in ACF blocks on side position
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 945
- Forks
- 197
- PR merge metrics
- No merged PRs in 30d
Description
The editor works correctly when it first loads, but after switching to the block options tab and then back to the page options, the WYSIWYG visual editor is all white, doesn't reflect the value of the field, and can't be interacted with. If you switch to the text tab of the editor it functions as expected.
This happens in the Gutenberg editor, I didn't test in the classic editor.
Steps to reproduce:
- Create a field group with a WYSIWYG editor and set the position to side
- Open a page
- WYSIWYG in the page options in the sidebar works correctly
- Switch from the page options in the side to the block options then back to the page options
- WYSIWYG no longer works
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
Start by reproducing the issue in the Gutenberg editor with a side-position WYSIWYG field, then compare the editor before and after switching between the page options and block options tabs. Done means the visual editor retains its value, displays correctly, and remains interactive after returning to the page options.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, wordpress
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100