When creating a content type and you would like to move the order of the fields so they show correctly cck does not create a option to move everything up or down in the list. You can move most stuff but something like Gmap you cannot move because the rown is not there to move. Now with me the location edit form is sitting right on top of my content type creation form and I cannot get it to move down. It also shows on top of my completed content form It's looks horrible and it's really annoying that you cannot move all the stuff around like menu items and the rest. Is it possible to fix this?

Comments

markus_petrux’s picture

markus_petrux commented
Component: CCK in core » content.module

I haven't used locations, so I'm not sure what you mean.

If these items in the node edit form are not CCK fields, then Locations needs to implement hook_content_extra_fields($type_name). This is how CCK knows it needs to add an extra item in the "Manage fields" screen, so it can be positioned. Otherwise, when CCK is installed the weight of other top level elements in the node form may behave erratically.

vip_sa’s picture

vip_sa commented

When you install a module then sometimes (not all the time unfortunately) it creates a row your content type's main field screen.(the screen where you can move fields up and down using your mouse). Now GMap does not create such a field that you can move up and down so now I have one big map sitting on top of my node creation page and I cannot move it down. No matter if I move the cck fields up or not they never go and sit on top of the gmap module's edit form. So why does certain modules create fields that you can move up and down and other don't? Is it a cck problem or a Gmap module problem? Guess with my luck it's a gmap module

Thanks for replying so quickly!

markus_petrux’s picture

markus_petrux commented
Status: Active » Closed (won't fix)

Since you have already filed an issue to the Gmap module queue, I think this one is "won't fix".

Once CCK is installed, it takes over the weights of all top level elements in the node edit form (and node view). But CCK cannot guess these extra elements by itself. Modules need to tell this information to CCK using hook_content_extra_fields($type_name).

For reference: #409144: content_extra_weights gets corrupted and breaks the ordering of form elements on node edit form

vip_sa’s picture

vip_sa commented

So can't I just set the weight of the gmap in the database to something that will make it appear lower in the node creation form?

samchok’s picture

samchok commented

The location module has a weight field under Locative information > Collection settings > Location form weight.
It is not really userfriendly... but it works (at least form me).