Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Important Custom Field content is hidden behind Extended Settings section #3141

Closed
maddisondesigns opened this issue Oct 25, 2017 · 3 comments · Fixed by #3147
Closed

Important Custom Field content is hidden behind Extended Settings section #3141

maddisondesigns opened this issue Oct 25, 2017 · 3 comments · Fixed by #3147

Comments

@maddisondesigns
Copy link

Issue Overview

When developers build sites for clients and utilise something like Advanced Custom Fields (ACF), the custom field content isn't considered as just secondary content. It's typically important page/post content that needs to be filled out when creating that particular page/post. This type of content shouldn't be hidden behind an Extended Settings panel, especially one that is initially closed as the end user isn't going to notice it.

The user should be able to view all their custom fields upon editing their page/post.

On top of this the Extended Settings section isn't scrollable which means that not all the custom fields are displayed.

The other annoying thing about having an Extended Settings section that simply opens and close is that it ends up covering the rest of the Gutenberg content.

gutenbergcustomfields1

Steps to Reproduce (for bugs)

  1. Install ACF
  2. Create multiple custom fields that get added to either a Page or Post
  3. Create new Page/Post or Edit existing Page/Post

Expected Behaviour

I should be able to scroll the page to view all my custom fields

Current Behaviour

Important page/post content is hidden from user

Possible Solution

Add Custom Fields to bottom of editor, just like it is currently, so that it can be viewed properly and isn't hidden from the user

macOS Sierrra 10.12.1
Firefox 56.0 (64-bit)
Gutenberg 1.5.1

@nicolinuxfr
Copy link

Same thing here, for custom fields I created myself (using the interface in the classic editor). I thought I would see these fields in the new meta box section of Gutenberg 1.5, but I only see what plugins are adding.

Is this standard behaviour ? Should I create a plugin for these fields ?

Here's what I have for a post, for instance :

capture d ecran 2017-10-25 a 12 08 10

@lukecav
Copy link

lukecav commented Oct 25, 2017

You can see a similar issue if you use Gutenberg with WooCommerce, when you add a new product the product data metaboxes are not visable until you click on Extend Settings.
new product extend settings wc

@kevinwhoffman
Copy link
Contributor

I don't see the Extended Settings wrapper serving a purpose other than to obfuscate meta boxes. The appearance of an expanded Extended Settings panel looks cluttered and confusing as multiple arrows are pointing up and down at each other while sidebar arrows point right.

image

Through WordPress 4.9, the user's expectation is to see expanded meta boxes when they open the editor. We could meet that expectation by displaying the meta boxes in their expanded state as top-level sections (not buried inside the ambiguous "Extended Settings" drawer).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants