Issue: Required custom fields improvements

Yes, this is annoying. I experienced this on the VW.org XF demo wiki while editing an old template page with the last revision occurring before custom fields were implemented.

Perhaps the simplest fix is to expand only the sections that have required fields.

If it can not be conditionally expanded, then perhaps the error message could specify the section? "Please enter a value for 2 required above the content fields: topfield, quality." Although if I am honest, this doesn't seem like a great approach.

Perhaps there is a more elegant solution, but I am not sure what that might be. I do not currently use VW custom fields on my own site nor have I really experimented with them.

One last observation: When editing template pages, the RTE for custom fields is locked in BB code mode (the same as the page itself). Unsure whether this is per design or not.

It's so much more obvious for a Xenforo thread custom field:

This is the fix I have considered in the past. I would also like the section expanded if there is an error (such as if the user collapsed it), but I don't think it is possible to modify XenForo's error handler in that way. In that case, perhaps the error message should also specify the section.

That is because the custom field you saw is not for the template itself, but will be provided to other pages by the template. As such, the field uses template syntax, the same as the template itself. If the custom field normally has only certain options, the input's description explains how to go about handling that.

It is possible to add custom fields to the template that are not provided to other pages (e.g. for info about the template), but this would be configured on the admin side.

In the next release, fixed the required field group being expanded only on new pages and pages where the field was recently assigned. This behavior has been changed to always expand the group by default if the group contains a required field. Also, the headings for groups containing required fields now hint "Has required fields."

In the next release, fixed the required field error message showing the phrase-name of the missing field rather than the phrase value. Also added the heading the field appears under to the error so that it's easier to locate if the heading is currently collapsed.

A related permissions escalation has also been addressed for the February security update.

Sounds brilliant. Thanks this will help a lot!