New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changed the order of the fields in Form Customization #16052
Conversation
Adding region to the table maybe is a good idea, it became more clear. But at the same time grouping by label |
I figured out how to display the region in the group title:
But this, in my opinion, is a strange solution, but it works :) |
Guys, I corrected the group label, and also left the regions in the grid (this is consistent with the setting of regions for TV and is clearer, as @alroniks pointed out). p.s. But I didn't understand why |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Works fine here. When is this xml file loaded into the database?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Works for me as well.
During the installation process, probably (not sure), the fields have moved, exactly as they are set in xml. BUT not Here is the condition - https://github.com/modxcms/revolution/blob/3.x/_build/resolvers/resolve.actionfields.php#L32 |
What does it do?
Before:
After:
The headings were called somewhere just "ID", somewhere "Region", which was confusing.
Now the "Region (ID)" is specified - now it is clear that this is a region, and its ID is involved in the rendering of forms.
Why is it needed?
Now clearer when working with regions in FC
Related issue(s)/PR(s)
#14226