Bug #60847
closed
displayCond depending on type=select
0%
Description
In my TCA I tried to add some displayCond to a field depending on a field that is of type "select":
$GLOBALS['TCA']['fe_users']['columns']['myNewField']['displayCond'] = 'FIELD:usergroup:=:2';
As it turns out displayCond does NOT work with the raw record (with usergroup="2") but with a version that's been rendered by the DataPreprocessor: usergroup="2|Name%20of%20my%20Usergroup".
Of course this is not as one would expect. A displayCond like
FIELD:usergroup:=:2|Name%20of%20my%20Usergroup
is not nice but does the job. Anyway it'll be more consistent with all other fields if the displayCond was applied to the raw data and not enforce such squabbling. Plus it'll be more consistent to renaming user records.
Updated by Mathias Schreiber about 9 years ago
- Category set to FormEngine aka TCEforms
- Assignee set to Christian Kuhn
@Christian Kuhn: idea?
Updated by Christian Kuhn almost 8 years ago
are you sure the target field is of type select and not of type group?
Updated by Christian Kuhn almost 8 years ago
- Status changed from New to Needs Feedback
could you hand in some example tca of both display condition field and target field of FIELD condition?
Updated by Riccardo De Contardi over 7 years ago
- Status changed from Needs Feedback to Closed
- Assignee deleted (
Christian Kuhn)
No feedback since the last 90 days > closing.
If you think that this is the wrong decision or experience the issue again then please reopen it or open a new issue with a reference to this one. Thank you.