- Issue created by @pameeela
- First commit to issue fork.
- Merge request !506Issue #3498658: Update node edit forms so the fields are consistently ordered β (Merged) created by riyas_nr
Reordered content type form fields to match the display order for better consistency and clarity.
Modified test files to verify the reorder change.
- πΊπΈUnited States phenaproxima Massachusetts
Thanks! And thank you for fixing the tests too. :)
I think we could even take this a step further and add some test coverage to confirm that the fields which are shared by the form and view displays are same-ordered. I'll take that on.
- πΊπΈUnited States phenaproxima Massachusetts
Added more test coverage to ensure that the displays actually match.
- πΊπΈUnited States phenaproxima Massachusetts
Looks like the added test coverage encountered some inconsistencies in the Person and Project content types! (Good thing I added it, eh?)
- πΊπΈUnited States phenaproxima Massachusetts
Alright - fixed those last two (made the forms match the rendered content).
-
phenaproxima β
committed e2e6a757 on 1.x authored by
riyas_nr β
Issue #3498658 by phenaproxima, riyas_nr, pameeela: Update node edit...
-
phenaproxima β
committed e2e6a757 on 1.x authored by
riyas_nr β
- πΊπΈUnited States phenaproxima Massachusetts
Merged into 1.x. Thanks!
Although this is a mildly annoying bug, it's certainly not a show-stopper that's causing WSODs in the wild. Besides, it is possible that there are people who like the existing (wonky) field order. So, for these reasons, I have decided not to backport this to 1.0.x.
Automatically closed - issue fixed for 2 weeks with no activity.