Project

General

Profile

Actions

Bug #92516

open

Symfony expressions/conditions doesn't work in user-tsconfig in context menu

Added by Dmitry Dulepov over 3 years ago. Updated about 2 years ago.

Status:
New
Priority:
Should have
Assignee:
-
Category:
TypoScript
Target version:
-
Start date:
2020-10-08
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
9
PHP Version:
Tags:
Complexity:
hard
Is Regression:
Sprint Focus:

Description

This is the same as resolved https://forge.typo3.org/issues/86229 but appliues to the context menu only in the page tree.

How to reproduce

Install EXT:impexp (composer: typo3/cms-impexp)
Have the following in User TSConfig:

[!backend.user.isAdmin]
    options.contextMenu {
        table {
            virtual_root.tree.disableItems := addToList(importT3d,exportT3d)
            pages_root.tree.disableItems := addToList(importT3d,exportT3d)
            pages.tree.disableItems := addToList(importT3d,exportT3d)
        }
    }

The condition will work fine anywhere except when the page tree is clicked to show the context menu. In that case the user will not be detected because user context is initialized before the Backend user itself.

As a result, import export will not be shown for admin user in the context menu.


Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Bug #86229: Symfony expressions/conditions doesn't work in user-tsconfigClosedFrank Nägler2018-09-11

Actions
Related to TYPO3 Core - Bug #90075: backend user symfony expressions not working in TSConfigClosed2020-01-09

Actions
Actions #1

Updated by Dmitry Dulepov over 3 years ago

  • Related to Bug #86229: Symfony expressions/conditions doesn't work in user-tsconfig added
Actions #2

Updated by Dmitry Dulepov over 3 years ago

  • Related to Bug #90075: backend user symfony expressions not working in TSConfig added
Actions #3

Updated by Simon Schaufelberger about 2 years ago

  • Category changed from Backend API to TypoScript
  • Complexity set to hard

I think conditions in general don't work in TSConfig. The solution is to set different configs in different backend user groups and then assign the users to the appropriate user group.

Actions #4

Updated by Dmitry Dulepov about 2 years ago

In general they did work, do work and should work. This functionality is there for ages but now it has newer syntax.

Like [4 in tree.rootLineIds] or [page["backend_layout"] == "pagets__Home"] or [usergroup("1")].

Actions

Also available in: Atom PDF