Hi
This is a great module and its really improved the look of my site, recently however I've experience a strange problem that I can't solve.
I have all of my vocabularies set with Custom display, the comma separated list at the top of the page. This works great for every content type but one. For some reason on just this one content type the tag display is forced to the bottom of the page, rather than the top. The display is still a comma separated list as I expect but its in the wrong position. I guess it must be an issue specific to this content type, since it works on all the others, but I can't imagine what could be affecting Term Display's output in this way.
To try and give you some details:
- The weight of each custom display is set to 0 (noting that the weight is for "advanced use only" and "can cause problems")
- There are two vocabularies enabled for the content type, both are localized
- The Pagination module is installed on the site and pagination is enabled for this content type
- The content type was created using cck and has three cck fields
- a text select list
- a text field
- a text area containing some php code by default
Non of these things however are particularly interesting since the other content types for which there is no problem all exhibit these details.
If any one can offer some suggestions on this confusing problem, they would be very much appreciated. Thanks.
Comments
Comment #1
asb commentedHi,
I can confirm this behaviour in Acquia Prosper.
Also I have no idea how to theme this "Custom display"; Firebug gives me an very ugly CSS around these tags:
My four vocabularies are scattered at the node's bottom, in between them there's a CCK fieldgroup. Sorry, I don't understand what's this supposed to accomplish. I'm getting significantly better results much easier and more understandable with this tutorial: Putting some order in your terms by Caroline Schnapp.
Greetings, -asb
Comment #2
Anonymous (not verified) commentedAm also having this issue. The list goes to the bottom instead of remaining at the top. Rearranging the Taxonomy Module field via editing the content type does nothing.
Comment #3
joachim commentedThis would probably be solved with #705806: Use CCK manage fields weight.