Bug #69892
closed
Condition usergroup in Backend does not work
0%
Description
In Backend condition "usergroup" does never match.
I debugged the code a little bit and find out that in TYPO3\CMS\Backend\Configuration\TypoScript\ConditionMatching::evaluateCondition() the value of $GLOBALS['BE_USER'] is null.
[usergroup = 3]
TCEFORM.mytable1 {
fieldxy1.disabled = 1
}
First I tried
page.TCEFORM.mytable1 {
fieldxy1.disabled = 1
}
as described in [[https://docs.typo3.org/typo3cms/TSconfigReference/UserTsconfig/TopLevelObjects/Index.html]]
But this also seems not to work, maybe another bug.
For now I'm under too much time pressure to do more diagnostics.
Updated by Wouter Wolters about 9 years ago
- Status changed from New to Needs Feedback
I just tested this here on current master and it works fine here.
The example I used was:
[usergroup=1]
TCEFORM.pages.doktype.removeItems = 6,254,116,255
[end]
Can you try this one?
Updated by Riccardo De Contardi almost 9 years ago
- Status changed from Needs Feedback to Closed
I think I can close this: there has been no feedback since the last 90 days; moreover, I have tried with the latest master:
both:
[usergroup=1] TCEFORM.pages.doktype.removeItems = 6,254,116,255 [end]
and
[usergroup=1] TCEFORM.pages.subtitle.disabled=1 [end]
and everything works as expected (I have even tried with a different usergroup (uid=2)).
If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.
You could also join the #typo3-cms channel in Slack if you still need support.
Thank you