The #weight doesn't have any effect. If you switch the "Format forms as table" setting off, then it works fine, but not with the table formatting.

Comments

tim.plunkett’s picture

Status: Active » Postponed (maintainer needs more info)

Order of which, the field collection items, or the field collections?
Given the case of a content type playlist, field collection of track, and field collection items of artist, title, and album.

Reordering the HEADERS of the table (artist, title, album) works.
Reordering the CONTENTS of field_collection_items (if you have a multiple artist field, rearranging individual artists for a track) works.

Reordering the tracks themselves does not work, but I haven't seen that work for any of the displays, and shouldn't be specific to this module.

singularo’s picture

Single field collection, with multiple columns, its an invoice, and the field collection table is for line items.
The columns are: date popup, qty, stock code, description, serial number, price

Moving any around in the design works, but in the edit form, they always come out in the order listed. The weights do appear to work on the output of the saved node, so only in the edit form does the issue appear.

tim.plunkett’s picture

Status: Postponed (maintainer needs more info) » Needs review
StatusFileSize
new554 bytes

Ah, now that's information I can work with!
Please try this patch (it's only a one-liner, you could probably edit it in yourself).

singularo’s picture

Status: Needs review » Reviewed & tested by the community

Yep, that solves it nicely. Thanks!

tim.plunkett’s picture

Status: Reviewed & tested by the community » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.