When I change the taxonomy weight in admin->content management->[node type]->manage fields I cannot move the field down.

This needs to be done to control the order of fields while inputting the node.

I can move it up, but cannot move it back down once its there.

Note that on the admin->content management->[node type]->manage fields page it appears to "stick", but on the input form for the node the taxonomy appears at the top no matter where I try to put it.

Comments

yched’s picture

yched commented
Status: Active » Postponed (maintainer needs more info)

Unable to reproduce on latest 6.x-2.x-dev.
What are the taxonomy-related modules enabled on your site ?
Does the problem persists if you disable them (except core's Taxonomy module, of course)

simonaustin’s picture

simonaustin commented
Version: 6.x-2.0-rc4 » 6.x-2.0-rc6

I have upgraded to rc6 and the problem still persists.

The only modules that I think might be related are directory, views and content templates, and the problem persists if I disable them.

If I disable all non-core modules with the exception of content (cck) the problem still persists.
Here is a complete list:
CCK, content templates (cck related), link (cck-related), number (cck), options widgets (cck), text(cck)
directory, pathauto, token, views, fivestar, and voting api

If I disable all non-core modules except for content (cck) and optional core modules other than taxonomy the problem still persists.

I had previously enabled the core book module, but have since disabled it. However I still notice that I am still able to create node of "book" type. I don't think that this is related, but thought I'd note it because it seems that there are still artifacts left in the DB from that module once being installed (there is no option to uninstall it).

Where in the DB are the values stored? Is the data serialized?

yched’s picture

yched commented

The weights for non-cck fields are stored in the {variable} table :
content_extra_weights_TYPE_NAME

confusi0n’s picture

confusi0n commented

I'm getting the same problem. I have no extra_weights table either.

John

simonaustin’s picture

simonaustin commented

the name of the table is "variable". Look for name like "%extra_weights%" (assuming you're using mysql).

simonaustin’s picture

simonaustin commented
Status: Postponed (maintainer needs more info) » Active

Here are the values from that field (the type name is "link"):

mysql> select * from variable where name like "content_extra_weight%";
+----------------------------+-----------------------------------------------------------------------------+
| name | value |
+----------------------------+-----------------------------------------------------------------------------+
| content_extra_weights_link | a:3:{s:5:"title";s:1:"1";s:10:"body_field";s:1:"5";s:8:"taxonomy";s:1:"7";} |
+----------------------------+-----------------------------------------------------------------------------+

From the looks of this, the taxonomy is weighted "7" so it should be at the bottom and not the top.

I am not sure why it is not obeyed.

mike_r1977’s picture

mike_r1977 commented

I can confirm this. While this is merely annoying, it does mean that the client is confused because the taxonomy field does not have a consistent position among content types, which is not ideal.

karens’s picture

karens commented
Status: Active » Postponed (maintainer needs more info)

I am unable to replicate this in the latest code. I did just commit a weight fix to -dev that could affect this if one of your fields had a weight of zero (in that case it is not that taxonomy had the wrong weight but that the other fields did), so see if using the latest -dev code with today's commits takes care of the problem. If you use the tarball, you'll have to wait until tomorrow to get a tarball with today's commits.

Lorbas’s picture

Lorbas commented
Version: 6.x-2.0-rc6 » 6.x-2.1
Priority: Normal » Critical

I have same problem, I cannot move the field down, how to fix this? It's really annoying

thx

slappy_thm’s picture

slappy_thm commented

Same issue here. I can reposition the taxonomy when I edit my content types, but it only applies weights that are lighter then the last. Now 1/2 my content types have the Taxonomy stuck as the first field.

Update: Found my solution by applying this patch:

http://drupal.org/node/356158#comment-1256979

Bartels-1’s picture

Bartels-1 commented

I'm experiencing the same issue with taxonomy and menu settings. Both of these fields remain at the top once arranged to that placement then subsequently rearranged.

Steps to reproduce:
1. Create new content type.
2. Add vocabulary to new content type. (I'm using tags)
3. Add fields to content type.
4. Move taxonomy and menu settings to bottom and save.
5. View content type.
6. Move taxonomy and/or menu settings up and save.
7. View content type.
8. Move taxonomy and/or menu settings to bottom and save.
9. View content type.

I'm also not finding any fieldnames containing 'extra_weight' in the variables table. I'm using Drupal 6.10.

markus_petrux’s picture

markus_petrux commented
Status: Postponed (maintainer needs more info) » Closed (duplicate)

Well, I believe this is a dup of #356158: Drag and Drop field weight assignment is buggy

Please, try latest 6.x-2.x-dev and see if it fixes the issue here. Otherwise, sorry and please re-open.