Bug #88360
open
Missing Slug when editors create a NEW page?
0%
Description
An editor creates a new page named "my New Page" e.g.
The editor has no right (should not have) to edit the slug-field in the BE
Calling this new page in the frontend shows the root page because there was no slug (e.g. "my-new-page" ) existing.
Updated by Benni Mack almost 5 years ago
- Status changed from New to Accepted
Yes. noticed this as well! Have to investigate. I guess it's somehow related to the "PseudoSiteDisplayCondition".
Updated by Christian Buelter almost 5 years ago
related to https://forge.typo3.org/issues/88224
Updated by Riccardo De Contardi almost 5 years ago
- Related to Feature #88224: Make it possible to hide slug field for editors / make it readonly added
Updated by Riccardo De Contardi almost 5 years ago
- Category set to Link Handling, Site Handling & Routing
Updated by Wittkiel Gruppe almost 5 years ago
Still a big problem in 9.5.8. Editors can't create new pages, slug is always empty.
Updated by Riny van Tiggelen over 3 years ago
Still occurs in 10.4.6
A nasty side-effect now is that when a user with permissions updates the slug, a redirect gets created for "/" to the new slug.
This means that the homepage of the current site gets redirect to the page, which is definitely not desirable.
Updated by Kurt Kunig over 3 years ago
Today I think that an editor (User) must have access to the slug-field by hiv be_user_group.
Reason:
An editor creates a master element with slug "master-element".
After that he copies this master (template) more than once into his element sructure and renames the copy-title e.g. into "This is my new element". The copied slug becomes "master-element1". Now - how should the editor modify the slug without access to the slug field !???