Epic #69347: EXT:form - Optimize form wizard
EXT:form - Reduce predefined form element fullname
The predefined form element fullname shows additional fields like suffix, prefix, middle which shall be disabled by default.
The most common use case is to have firstname and lastname here.
Updated by Bjoern Jacob almost 6 years ago
- Tracker changed from Bug to Feature
I don't think that this is a bug. IMHO there should be a way to make this configurable or at least have the possibility to remove all the fields one does not need. We're thinking about a solution and like to discuss it here. Please stay tuned :)
Updated by Sebastian Wagner over 5 years ago
- File TYPO3_Forms_[TYPO3_CMS_7.5.0-dev]_-_2015-08-28_14.11.11.png TYPO3_Forms_[TYPO3_CMS_7.5.0-dev]_-_2015-08-28_14.11.11.png added
- % Done changed from 0 to 20
We could easily switch prefix, middlename and suffix to disabled per default.
This arises an UX problem though:
Users won't recognize the switches to enable them again because they are hidden in the various-collapsible.
We'll try to refactor all properties into one collapsible or open the various-one as initially.
In order to nudge users about disabled prefix-fields we tried to just disable them, wich leads to them beeing hidden in the frontend as well.
In this context an other problem arose too:
properties in e.g. the various-collapsible only work for their respective elements whose function depends uppon their name.
This results in a property called "prefix" will ever only work in conjunction with (full)name-elements because we are missing at least one level of abstraction here.
In general there is to much logic placed within the ext-js-application.
Updated by Bjoern Jacob about 5 years ago
- Status changed from New to Closed
- Assignee deleted (
- Target version deleted (
The form wizard will be rewritten in version 8. The current wizard will not be touched anymore. Right now, we don't see any use case for having such complex predefined elements in the future.