Posted by beeradb on March 7, 2009 at 7:48pm
Jump to:
| Project: | Drupal core |
| Version: | 7.x-dev |
| Component: | taxonomy.module |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (won't fix) |
Issue Summary
Consider automatically creating a block for each vocabulary. During user testing users went straight to the block configuration screen when trying to complete task 6 (http://drupalusability.org/node/32), hoping to find a block already available for them to use. Consider providing this block by default, similar to what we do with menus.
Comments
#1
Menus have no other function than to be displayed. If we display all terms in a vocabulary, do we provide page or block views (because both are wanted). Also, what kind of options do we offer? See Vocabulary Index for the two technical implementations. There are two ways to display Taxonomy data: at a single page (tree view) or at multiple pages (browsable).
#2
We need another way to create blocks for menu, aggregator feeds and (apparently) taxonomy. Creating a block automatically simply doesn't scale.
That was one of the issue we faced when upgrading drupal.org, that manages 200+ feeds via the aggregator module.
#3
#430886: Make blocks entities would handle the 'create a block for everything' issue. Let's lots of vocabulary block modules in contrib, I think it's fine for them to handle this.