AdvancedCustomFields / AdvancedCustomFields/acf
Gutenberg and static page template based conditional logic issue
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 945
- Forks
- 197
- PR merge metrics
- No merged PRs in 30d
Description
I am using the Flexible Content field in a static page. Via conditional logic, this field is configured to show up when a custom template is selected from the Template drop down. With Gutenberg, the Flexible Content field is always visible regardless of what template is selected. Works as before with Classic Editor.
- WP 5.0.2
- ACF 5.7.9
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 report with WordPress 5.0.2 and ACF 5.7.9: use a static page, a custom template, and a Flexible Content field whose conditional logic depends on the selected template. Compare Gutenberg with Classic Editor, then trace the conditional-logic behavior. Done means the field visibility follows the selected template in Gutenberg as it does in Classic Editor.
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
- 28/100