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

Category Selection Shows Truncated List #5820

Closed
brysont opened this issue Mar 27, 2018 · 6 comments
Closed

Category Selection Shows Truncated List #5820

brysont opened this issue Mar 27, 2018 · 6 comments
Labels
Core REST API Task Task for Core REST API efforts [Priority] High Used to indicate top priority items that need quick attention [Type] Bug An existing feature does not function as intended

Comments

@brysont
Copy link

brysont commented Mar 27, 2018

Issue Overview

When assigning category(s) to a post, only 32 categories show up. 171 categories in all, but only a random first 32 appear in the editor (possibly sorted by use?).

And yes, that many. Sports site covering all professional American leagues and teams = 171 categories.

Steps to Reproduce (for bugs)

  1. Create 33 or more categories
  2. Create a new post and try to assign each of the 33+ categories

Using Chrome 65 on a Windows 10 machine (all updates current). WordPress 4.9.4, also fully updated. Gutenberg 2.4.0.

Expected Behavior

All categories should be visible, likely via use of scrolling overflow for the parent .components-panel__body.is-opened div to the .editor-post-taxonomies__hierarchical-terms-choice div. The list of categories shown is truncated to 32 results, as adding overflow: scroll; or overflow: auto; to the CSS doesn't help.

At the very least, it should work like the category list in the classic editor, loading all into a scrollable box. A possible improvement would be to load all parent categories in that manner, each one able to be clicked and expanded to show child categories for selection. On an edited post (categories already assigned), classic editor functionality could be used (pinning assigned categories to the top of the list, out of context), or the appropriate parent category(s) could initialize expanded, to show the assigned children.

@karmatosed
Copy link
Member

This looks like a similar issue to #4022 so closing for that. Thanks.

@brysont
Copy link
Author

brysont commented Mar 27, 2018

Negative. #4022 refers to content output of a category list (frontend).

My issue is about post metadata selection (backend).

@karmatosed
Copy link
Member

Thanks for clarifying. I am going to cc someone in to double check they aren't related and try and get some progress for you - reopening while that happens. @pento do you have any insights here?

@karmatosed karmatosed reopened this Mar 27, 2018
@jeffpaul jeffpaul added the [Type] Bug An existing feature does not function as intended label Mar 29, 2018
@danielbachhuber danielbachhuber added this to the Core API milestone Apr 11, 2018
@danielbachhuber danielbachhuber added the Core REST API Task Task for Core REST API efforts label Apr 11, 2018
@danielbachhuber
Copy link
Member

It's the REST API pagination issue. We can keep this open until it's resolved.

@richardiriwn
Copy link

I have a similar problem. Web sites highly dependent upon categories for navigation. However with Gutenberg enabled, I only see a list of 2 out of several hundred when I create or edit post or page.
Nice looking editor!

@Karlheinzniebuhr
Copy link

For me, they don't show up at all. None, zero visible categories.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Core REST API Task Task for Core REST API efforts [Priority] High Used to indicate top priority items that need quick attention [Type] Bug An existing feature does not function as intended
Projects
None yet
Development

No branches or pull requests

6 participants