Posted by tweaker on May 2, 2006 at 4:37am
4 followers
Jump to:
| Project: | Flexinode |
| Version: | master |
| Component: | User interface |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
Druapl 4.7
Flexinode CVS
I set up several fields, then went in to assign them weights. At this point the problem can be viewed two ways.
1) Title does not stay at the Top
or
2) No way to assign a weight to Title
in other words - as I assigned weights the Title would start to float down in the display of fields and no weight factor to correct this.
thanks
Comments
#1
Been playing with this a bit.
Giving Catagories a high weight factor seems to add to the effect, just not sure how to define the realtionship yet.
#2
From what I can see the title has some kind of hard coded weight of -5. Although I don't know where it gets this from. Also, 'Categories' seem to be given a weight of -2 (for the purposes of ordering in the entry form on the 'create content' page).
Although, it displays differently when viewing a node, due to the template explicitly placing the title and categories.
#3
This could be a related issue:
Fields sorting with weights does not work
[58391]
http://drupal.org/node/58391
#4
OK, it seems this isn't a flexinode specific issue.
See a bit more info here:
In node edit page, "Categories" form has wrong weight
http://drupal.org/node/45089
#5
grep gives me this:
node.module:1607: $form['title']['#weight'] = -5;
There is probably a better way to do this, but it looks like it is a 'by design' issue. The whole way weights work (for node fields) could probably do with some re-thinking, but that is probably something that will come up with CCK as things develop (I guess).
#6
Doesn't seem like this should gate release of 4.7 Flexinode.
#7
thank you for the time you spent looking into this.
Once a person understands why this is happening, just a little bit of reworking and planning how to use the weights, this issue can be worked around. It just caught me off guard the first time.
#8
This is a missing feature in Drupal itself.
We could try to make some flexinode feature from this: