Feature #88224
closed
Epic #90674: Backend UI not reflecting permissions
Make it possible to hide slug field for editors / make it readonly
0%
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).
Updated by Christian Buelter over 5 years ago
related to https://forge.typo3.org/issues/88360
Updated by Riccardo De Contardi over 5 years ago
- Related to Bug #88360: Missing Slug when editors create a NEW page? added
Updated by Riccardo De Contardi about 5 years ago
- Category set to Site Handling, Site Sets & Routing
Maybe EXT:sluggi can be of help here in the meanwhile.
https://extensions.typo3.org/extension/sluggi/
Updated by Benni Mack about 5 years ago
- Related to Bug #89060: Automatic generating a slug fails if editor has no permission added
Updated by Georg Ringer 6 months ago
- Related to Bug #92202: Hiding field colPos through access lists breaks dragging content between columns added
Updated by Georg Ringer 6 months ago
- Status changed from New to Resolved
with #92202 the exclude has been removed from the slug field and it is always there.
hiding important fields with e.g. tsconfig can always lead to strange behaviours, imagine hiding colPos for layouts with multiple colPos values, or hiding ctype field