Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I think the title says it all. Just for clarification see the attached screenshot.
Comment | File | Size | Author |
---|---|---|---|
screenshot_01.jpg | 220.49 KB | rontec76 |
Comments
Comment #1
rontec76 CreditAttribution: rontec76 commentedComment #2
JacineYeah, this is one of the most annoying things in d7. These terms should be in a list, not just a bunch of divs.
Comment #3
Jeff Burnz CreditAttribution: Jeff Burnz commented@rontec76 - you got a patch coming for this one? Be good to resolve this.
@Jacine - we could make them lists, what you think? It does mean adding the suggestions - but I've been thinking about coming in with a late breaking patch for D7 to add suggestions per field-type to make this a hell of lot easier. I've been using...
Comment #4
Jacine@Jeff I think suggestions are a great idea. If you post up an issue let me know and I'll chime in to support.
Either way, we should definitely make this a list IMO.
Comment #5
Jeff Burnz CreditAttribution: Jeff Burnz commentedOK, I posted an issue - lets see how this fly's #784792: Field Type Template Suggestions
Comment #6
Jeff Burnz CreditAttribution: Jeff Burnz commentedoh btw, I'm doing with this with Bartik on local host already - applying the patch from the above issue and using this in template.php
Comment #7
jensimmons CreditAttribution: jensimmons commentedI'm all for overridding core output to make these be the
Comment #8
joachim CreditAttribution: joachim commentedDon't reinvent the wheel -- use http://api.drupal.org/api/function/theme_links/7
Comment #9
Jeff Burnz CreditAttribution: Jeff Burnz commentedUmm, so your saying using theme_field to theme a field rather than theme_links is reinventing the wheel?
Say wha?
Comment #10
joachim CreditAttribution: joachim commentedIn that theme_links makes you a UL of inline links.
Comment #11
Jeff Burnz CreditAttribution: Jeff Burnz commentedOK, I see, but really the issue cuts deeper than just a UL - its about using any markup we want in whatever field type. BTW sorry if I sounded a bit rude (now I read again) I wasn't meaning to.
Comment #12
joachim CreditAttribution: joachim commented:D
Hmmm they're a long list on Garland too.
I think we should move this to core, and fix it in either taxonomy module or FieldAPI rather than every theme having to do the same work.
Comment #13
Jeff Burnz CreditAttribution: Jeff Burnz commentedShould we mark this as a duplicate of #784792: Field Type Template Suggestions
Comment #14
joachim CreditAttribution: joachim commentedLooks like, yes
Comment #15
Jeff Burnz CreditAttribution: Jeff Burnz commentedOK, I'll mark this as duplicate of #784792: Field Type Template Suggestions since the other issue is really questioning this for core.
Just to clarify something that has not been stated - if you do want field items inline you can select this in the Display Options for the field. However this is about HTML, the display options merely change the display using CSS.
Comment #16
webmatter CreditAttribution: webmatter commentedThanks for the hint on the bartik function ... works great. Now terms are an ul list as they should be :)
Comment #17
osopolarBTW: The Fences module will help you to eg. render the taxonomy terms as a list.
Comment #18
mlr1980 CreditAttribution: mlr1980 commentedI'm having this same obnoxious issue on a D7 dev site I'm building with Corporate Clean. I've tried tinkering with the CSS, as well as the settings on both the Text Formatter and Taxonomy Formatter modules but for the life of me, I can't figure this out. I can either get the terms unlinked, on one line, separated by commas, or I can get them linked, on different lines with a comma in between. Does someone know of the fix for this? It's driving me nuts. Thx in advance.
Comment #19
redytravis CreditAttribution: redytravis commentedjust float the divs to the left then use jquery.
jQuery("div.field-name-field-tags .field-items .field-item a:not(div.field-name-field-tags .field-items .field-item:last-child a)").append(", ");