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

Blocks never used before are appearing under Frequent #5956

Closed
2 tasks
chrislema opened this issue Apr 3, 2018 · 1 comment
Closed
2 tasks

Blocks never used before are appearing under Frequent #5956

chrislema opened this issue Apr 3, 2018 · 1 comment

Comments

@chrislema
Copy link

Issue Overview

After adding several new gutenberg block plugins to my site, I am presented with several new blocks in the Frequent section of the block selector. Since I've never used them before, I don't believe they belong there.

Steps to Reproduce (for bugs)

  1. Activate Gutenberge
  2. Activate additional Gutenberg block plugins (like this one: https://wordpress.org/plugins/stackable-ultimate-gutenberg-blocks/)
  3. Create New Post
  4. Click on the Plus sign and notice that there are new blocks in the Frequent section

I was using Chrome 64 on MacOs 10.13

Expected Behavior

I believe that the only blocks that should show up under Frequent are those that I have actually used. Preferably, more than once (hence the term, frequent).

Current Behavior

Right now, it looks like plugins can determine on their own how to categorize their blocks. If everyone puts theirs in Frequent, the designation will become dramatically less valuable.

Possible Solution

Limit blocks entry into that section that have been used more than once.
Alternatively, measure how often every block is used and only present those in the top 10%.

Screenshots / Video

Related Issues and/or PRs

Todos

  • Tests
  • Documentation
@noisysocks
Copy link
Member

noisysocks commented Apr 4, 2018

Thanks for your feedback, @chrislema!

Blocks that have not been used will appear under Frequent by design, but I appreciate that this is confusing. I think our simplest path forward is to rename the tab to something like Suggested. I went into a little detail about how we pick these blocks here: #5627 (comment)

Closing this for now as it's a duplicate of #5627.

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

No branches or pull requests

2 participants