Project

General

Profile

Actions
Copy link

Bug #88360

closed

Missing Slug when editors create a NEW page?

Added by Kurt Kunig over 5 years ago. Updated 5 months ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
Site Handling, Site Sets & Routing
Target version:
-
Start date:
2019-05-15
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
9
PHP Version:
7.0
Tags:
slug, default slug
Complexity:
Is Regression:
Sprint Focus:

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.

Related issues 3 (0 open — 3 closed)

Related to TYPO3 Core - Feature #88224: Make it possible to hide slug field for editors / make it readonlyClosed2019-04-26

Actions
Related to TYPO3 Core - Bug #92202: Hiding field colPos through access lists breaks dragging content between columnsClosed2020-09-04

Actions
Has duplicate TYPO3 Core - Bug #89060: Automatic generating a slug fails if editor has no permissionClosed2019-09-02

Actions
Actions
Copy link
 #1

Updated by Benni Mack over 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".

Actions
Copy link
 #3

Updated by Riccardo De Contardi over 5 years ago

  • Related to Feature #88224: Make it possible to hide slug field for editors / make it readonly added
Actions
Copy link
 #4

Updated by Riccardo De Contardi over 5 years ago

  • Category set to Site Handling, Site Sets & Routing
Actions
Copy link
 #5

Updated by Wittkiel Gruppe over 5 years ago

Still a big problem in 9.5.8. Editors can't create new pages, slug is always empty.

Actions
Copy link
 #6

Updated by Riny van Tiggelen over 4 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.

Actions
Copy link
 #7

Updated by Kurt Kunig over 4 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 !???

Actions
Copy link
 #8

Updated by Georg Ringer 6 months ago

  • Has duplicate Bug #89060: Automatic generating a slug fails if editor has no permission added
Actions
Copy link
 #9

Updated by Georg Ringer 6 months ago

  • Related to Bug #92202: Hiding field colPos through access lists breaks dragging content between columns added
Actions
Copy link
 #10

Updated by Georg Ringer 6 months ago

  • Status changed from Accepted 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

Actions
Copy link
 #11

Updated by Benni Mack 5 months ago

  • Status changed from Resolved to Closed
Actions
Copy link

Also available in: Atom PDF