contao/issues — Issue #450: Upon TYPE change in FORM Generator, palette does not show correct for TYPE, when errors
Author: importer
Created: 2011-11-24 12:50:22+00:00
State: open
Labels: backend, Defect, Invalid

This happens in all TL, so its a general bug. To reproduce:

Go to the Form Generator:
- Click on the (+) to add a new field
- DO NOT enter the field name (leave blank)
- Change the TYPE of field to Select Menu

Notice that the TYPE HAS changed, however the palette is still showing the previous palette with errors from the previous submission.

This is particularly annoying, because some form fields do not even HAVE a field name, but because the default option requires it, you cannot add a HTML/Explanation field without first entering a fieldname.

Also, the fieldname for HTML/Explaination/etc. is displayed, even though its completely optional for these types of records.

This is also affecting other modules like the catalog, because people change the field's TYPE before entering a valid column name (similar to field name in Form Generator), and then the error is generated for the previous palette, even though the user now thinks he has changed the type, because the type drop-down shows the new type together with palette for the previous-error type.

--- _Originally created by thyon on January 26th, 2009, at 08:21am (ID 450)_