Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.It appears this module is not compatible with CCK's theming standard (field.tpl.php), instead relying on hardcoded
's on lines 230 and 238 of content_taxonomy.module
If I'm wrong on this or there is a way to get this working, any feedback or documentation on this would be much appreciated as I'm currently having to directly edit the formatting in content_taxonomy.module, something I've managed to avoid from doing with any other module so far.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | contentax1.patch | 2.27 KB | Ozeuss |
Comments
Comment #1
Raving commentedSorry, that's "hardcoded
<br />'s" :)Comment #2
buddaYes those pesky hardocded BR tags are quite annoying, can they be slipped in to a theme function so i can get rid of them neatly?
Comment #3
Ozeuss commentedThe problem lies in the fact that content_taxonomy uses the load $op in hook_field but not the view $op. So, data is loaded differently, but cck loads the field as default, which requires the "for each" loops in the field_formatter function.
This patch adds a view $op to the hook_field function, and iterates it correctly- sends a 'tid' variable to the formatter function, which then loads the term object. in other words- the for each loop in field_formatter is 'bumped' into content_taxonomy_field, and is called the number of objects loaded by the module.
Seems to work for me, please test.
Comment #4
Raving commentedSeems to work for me, on the latest version, too :)
Comment #5
ckngThe patch makes some fields not displaying on certain view.
Simply removing the
<br />does not seems to cause other problem.Comment #6
anthonym commentedI second the suggestion to make this a themeable function. Just removing the line break might suit every purpose. Comma-separated terms would be nice for instance... Any ideas on how to accomplish this?
Comment #7
smitty commentedSeems to be fixed in version of 2008-Jul-07.
Comment #8
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.