Unable to move content taxonomy field [#873102]

What a great module - thank you so much for contributing it!

I'm having a problem with one field. I have a node which has multiple cck fields of varying types (node reference, integer, computed, text, user reference, date - yeah, the whole kitchen sink). There are also two content taxonomy fields, "x" and "y". Everything is working beautifully except "y" seems to have attached itself to "x". I can move both of them around with no problem, but when I save the position data, "y" is repositioned on top of "x", no matter where I move "x".

Any ideas?

Comment	File	Size	Author
#2	ArrangeLikeThis.jpg	26.39 KB	MamaGubs
#2	AfterSaveGetThis.jpg	17.52 KB	MamaGubs
#1	af-2-vocabs.png	6.52 KB	richardp
#1	af-2-vocabs-fieldset.png	10.27 KB	richardp

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

richardp CreditAttribution: richardp commented 3 August 2010 at 23:26

File	Size
af-2-vocabs-fieldset.png	10.27 KB
af-2-vocabs.png	6.52 KB

I'm sorry to hear it's causing problems with the taxonomy. (Though I'm happy to hear it appears to work for everything else!)

I have tested it out on my side, but can't seem to replicate the problem. When both taxonomy are simply set as "tags" (and there is an auto-complete textfield) they are connected, but save and load correctly -- not on top of each other. When I set one or both to be "multiple select" then it places them in a fieldset, which behaves the normal fieldset way.

I have included screenshots of both of these states.

The only advice I can give you right away is to try clearing your drupal and browser cache, as it sounds like a CSS problem to me. If that doesn't work, could you provide a screenshot of the problem?

Richard

PS: As for multiple taxonomy fields being "stuck" together, this is sort of the way Drupal prepares them (they are in the same index of the $form array). I decided to leave them that way for the time being, though this might be something I change in future versions on this module. It depends on the interest -- in the meantime, you can always manually edit your site's CSS to force one of the taxonomy fields into another spot.

Comment #2

MamaGubs CreditAttribution: MamaGubs commented 6 August 2010 at 14:51

File	Size
AfterSaveGetThis.jpg	17.52 KB
ArrangeLikeThis.jpg	26.39 KB

Hi Richard,

Thanks for the quick response. It led me to fiddle more with the field widgets and I realized that the problem is not with the content taxonomy field type, but with the Hierarchical Select widget. I can have one of these fields use that widget, but not both. As soon as both are using the widget, one ends up anchored to the other. I've included screen shots.

It's definitely not a cache issue. Lord knows I flush all caches more than anyone has a right to :-)

Comment #3

richardp CreditAttribution: richardp commented 6 August 2010 at 14:56

Status:

Active

» Needs work

Interesting. I hadn't ever heard of the Hierarchial Select module before-- it looks cool. I will install it on my dev box and see if I can make arrange_fields work with it.

I will post here if I make any progress.

Thanks!
Richard

Comment #4

MamaGubs CreditAttribution: MamaGubs commented 6 August 2010 at 15:53

Yes, it's a great widget. It saved my hide with the taxonomy field, because I use Node Auto Term to create a term for every subproject - the list of terms was getting huge!

Thanks for the help - I'll watch the thread for further developments.

Comment #5

dre788 CreditAttribution: dre788 commented 16 March 2011 at 01:21

Has there been any updates on this matter? Just tried this module and got the same problem with hierarchical select.

Comment #6

richardp CreditAttribution: richardp commented 16 March 2011 at 16:55

No, i'm sorry, I have not been able to look into this issue yet. HS places itself in the $form array in an unusual way which Arrange Fields can't easily integrate with, and I just haven't been able to sit down and try to get it working.

As always, patches are welcome if anyone else out there reading this might want to take a stab at it ;)

Richard