The combination of several circumstances justify this:

  1. CCK isn't in core, so I can't provide a *consistent* interface for configuration HS form items. Due to this lacking consistency, it might be hard for the user to find the configuration form for a specific HS.
  2. The Drupal 5 CCK widget configuration system is too limited.
  3. Views' exposed filters will never use the CCK interface for widget configuration.

So I will provide an overview page, with a table consisting of the following columns:

  • entity type (currently either node or view)
  • entity id (if form type is node, then the node type, if form type is view, then the view name)
  • hierarchy type (the name of the module that implements this HS, e.g. taxonomy, hs_content_taxonomy, hs_views_taxonomy)
  • hierarchy id (in the case of the Taxonomy implementation: the vocabulary name, in case of a CCK field: the CCK field name)
  • link to config form

e.g.:

Entity Type Entity ID Hierarchy Type Hierarchy ID Configuration Form
node Story Taxonomy Cars configure
node Blog Post Content Taxonomy Categories configure
view tracker Taxonomy Cars configure

To collect the necessary information to be able to generate this, I will have to create an additional hook.

Comments

wim leers’s picture

After some more thought:
- Entity ID -> Entity
- Hierarchy ID -> Hierarchy
- also an "export" link, to export the settings
- likewise for "import"

wim leers’s picture

Status: Active » Fixed

Done!

Anonymous’s picture

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.