Hello Nedjo, dear community,

I've been looking for a displaying taxonomy terms as a CCK fields feature for a while. Now I get the point that the great yet underdevelopment term_display.module could make it.

This new feature would indeed allow much more flexibility, and great user-friendly advanced design options. Such as precise weighting and display options of taxonomy terms anywhere within the content (node, views, panels and more).

I guess that this feature would consist in the implementation of a hook for CCK, and therefore in a quasi-complete rewriting of the code. Isn't it?

But then tons of related modules could benefit of the term_display.module great design feature... that is to say extended to any of the taxonomy? CCK, views, panels and more .module... and any of their related's! Total control!

For example, the feature would allow to display terms as classified metadata (such as in field groups) instead of as a vague node bottom cloud.

In my case, the workaround for achieving this example is, I admit, horrible: I removed the "links" div from my node template so that they don't appear messy down there, and created CCK_taxonomy.module fields to display them whever I want... but without their link feature! (Yes, info's necessary, but it's not sufficient!!!)
So that finally, the node editors have to select the data twice, with no automatic guaranty the work's done... and with no link feature...

Screenshots :

1- metadata_WITHOUT_term_display.png shows my current situation.

2- metadata_WITH_term_display.png shows how it's actually quite hard to display the term_display.module terms with their unrelated weight: without a CCK hook, there's no preview in edit page, nor per-node-type CCK fields weighting, ... Imagine the benefits if term_display.module terms showed up into field groups, or any other CCK and content management related module...!

In this case 2-, the METADONNÉES DU CONTENU and METADONNÉES DU FICHIER tabs (thanks to -Nedjo and his dev/support of- the cck_fieldgroup_tabs.module and the jstools.module) would contain my metadata term just at the right spot, regardless of the node type, and just as a cck term... No more need of entering my data twice! No more need of php_templating! Huge benefit for any content management module regarding taxonomy! cck_term, that could be the name of a newborn .module!

What do you think?

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

nedjo’s picture

I see the potential benefit, but it's far beyond what I want to take on in this module.

Note that current discussions about bringing CCK fields into core for D7 include consideration of converting node taxonomy to a CCK-style field.

doc2@drupalfr.org’s picture

Wow!!! This is a great perspective of benefits to my point of view, but definately to many users' I guess for it's brought to drupal core features development!

If you know where to easily find a link to some main discussion about the topic you mention, could you just post it down there please?

Summit’s picture

Subscribing, greetings, Martijn