AdvancedCustomFields / AdvancedCustomFields/acf
Gutenberg compatibility for "Hide on screen" settings
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 945
- Forks
- 197
- PR merge metrics
- No merged PRs in 30d
Description
Description
Each field group contains a setting called "Hide on screen". This setting allows a user to select from a list of known "elements" on the page such as Permalink, Excerpt, Revisions, Format, etc.
Developers enjoy this setting as they can use it to hide core metaboxes from within the field group.
For example, you can create a field group called "Home" with some custom fields, and then hide all the WP default metaboxes (except the publish box). This makes the edit screen look highly customized with little effort.
To do this, we use CSS to hide these "elements".
Issues
- Our CSS can no longer can target these elements due to changes in the Gutenberg HTML markup. It is not possible to target a specific panel via CSS.
Questions
- How can we hide / show the following "elements"?
Permalink
Content Editor (not sure if this is possible now)
Excerpt
Discussion
Comments
Revisions
Slug
Author
Format
Page Attributes
Featured Image
Categories
Tags
Send Trackbacks - Can we still achieve this via CSS, or can we use the JS API?
- These "hide on screen" settings update via the Dynamic metaboxes feature, so we need the ability to hide an "element" and then show it later.
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
No files or tests are named. Start by reviewing the Gutenberg editor markup and JS API, alongside the Dynamic metaboxes issue (#111), to determine how the listed elements can be identified and controlled; done means Hide on screen can hide and later show the supported elements reliably.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, wordpress
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100