Project

General

Profile

Actions

Feature #88224

open

Epic #90674: Backend UI not reflecting permissions

Make it possible to hide slug field for editors / make it readonly

Added by Christian Buelter about 5 years ago. Updated about 4 years ago.

Status:
New
Priority:
Should have
Assignee:
-
Category:
Link Handling, Site Handling & Routing
Target version:
-
Start date:
2019-04-26
Due date:
% Done:

0%

Estimated time:
PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

In our projects we do not want to give write access to the page slug to certain backend groups.

But disabling the field via "exclude fields" leads to no slug being generated at all (slug field remains empty).

It would be great if slug generation would work without having access to the slug field or if the slug field could be readonly (which currently isn't possible also).


Related issues 2 (2 open0 closed)

Related to TYPO3 Core - Bug #88360: Missing Slug when editors create a NEW page?Accepted2019-05-15

Actions
Related to TYPO3 Core - Bug #89060: Automatic generating a slug fails if editor has no permissionNew2019-09-02

Actions
Actions #2

Updated by Riccardo De Contardi almost 5 years ago

  • Related to Bug #88360: Missing Slug when editors create a NEW page? added
Actions #3

Updated by Riccardo De Contardi over 4 years ago

  • Category set to Link Handling, Site Handling & Routing

Maybe EXT:sluggi can be of help here in the meanwhile.

https://extensions.typo3.org/extension/sluggi/
Actions #4

Updated by Benni Mack over 4 years ago

  • Related to Bug #89060: Automatic generating a slug fails if editor has no permission added
Actions #5

Updated by Riccardo De Contardi about 4 years ago

  • Parent task set to #90674
Actions

Also available in: Atom PDF