I created some fields and then a pagebreak and then changed the order of the fields.
But all fields displayed always on the 1st page.
After deleting them and the pagebreak I created another pagebreak and after that the needed fields for the 2nd page.
Now it works.
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | webform_pagebreak7.patch | 652 bytes | quicksketch |
| #5 | webform_pagebreak.patch | 634 bytes | james.elliott |
| #2 | 2011.11.17_webform1.png | 26.68 KB | drupa11y |
Comments
Comment #1
theard commentedIsn't this behavior that is desired.
Why would you want a page without any fields on it?
Comment #2
drupa11y commentedthink this is a misunderstanding.
Another example:
- I have a form with 2 pages and now add 2 fields I want to add on page 1.
- I reorder the 2 additional fields on the top of the field-queue and save.
But the 2 fields display not on page 1 but on top of page 2 which means that reordering does not work correctly after a pagebreak is created.
Attached the screens, hope you understand now.
Comment #3
ehalber commentedI am confirming this bug.
Comment #4
pheno commentedConfirmed.
I was creating a form and thought to add page breaks later after major components had been setup. Form seemed to structure components according to cid (component id I think) which is the automatic index creating key. It needs to be weight.
Tried looking for the query that gathers and orders components, and got lost.
Comment #5
james.elliott commentedI've done some work on this issue. The diagnosis I came across was that when the components are being pulled from the db they aren't being ordered by weight. This patch adds weight ordering to the query.
Comment #6
james.elliott commentedOops, needs review
Comment #7
quicksketchLooks good to me, the original D6 query is this:
So we need to order not just by weight by also by name for consistency between versions. I've committed this patch. Thanks all.