Actions
Feature #62554
closedEXT:form - OptionElement class improvment
Status:
Rejected
Priority:
Should have
Assignee:
-
Category:
Form Framework
Target version:
-
Start date:
2014-10-30
Due date:
% Done:
0%
Estimated time:
PHP Version:
Tags:
Complexity:
Sprint Focus:
Description
after line 87 in the function checkFilterAndSetIncomingDataFromRequest the value of the element is set to it's ID if it's empty.
this does not convey anything about the data if the form submit is handled by a different script/url. it would make much more sense to set it to something akin to the data. like:
if ($this->value === '') { $value = preg_replace('/\\s/', '_', (string) $this->data); $this->value = preg_replace('/[^a-zA-Z0-9_\\-]/', '', $value); $this->setAttribute('value', $this->value); }
or - if the id as value is needed somwhere else in the sysext, there should be a TS configuration option for the FORM object or the SELECT object - like
lib.form = FORM lib.form.optionsDefaultDataFromValue = 1
or
lib.form = FORM lib.form.10 = SELECT lib.form.10.defaultDataFromValue = 1
Updated by Riccardo De Contardi about 9 years ago
- Category set to Form Framework
Updated by Björn Jacob about 9 years ago
- Subject changed from sysext form: OptionElement class improvment to EXT:form - OptionElement class improvment
Updated by Björn Jacob almost 9 years ago
- Status changed from New to Rejected
I'm rejecting this feature. There are several reasons for it:
- This feature won't come for 6.2 and 7 LTS (since it's a feature).
- For v8 we're planning to introduce new ways to extend and change the behavior of EXT:form programatically. There will be generic ways to hook the processes. The proposed ideas of this issue are not generic enough.
- Since the rewrite of EXT:form the whole process has changed. We're now relying on extbase and fluid. There are some limitations when it comes to interaction with 3rd party scripts.
So please stay tuned. We're having a lot of stuff coming with v8 on the roadmap.
Actions