Project

General

Profile

Actions

Bug #89485

closed

Editing a slug field on a root page (page with SiteConfiguration) is not possible if parent uid of this root page is > 0 and TreeRoot has no site configuration

Added by Robert Wolle over 4 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Link Handling, Site Handling & Routing
Target version:
-
Start date:
2019-10-23
Due date:
% Done:

100%

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

Description

Current situation:
We have a lot of pages in our Typo3 system. Therefore we organize them in different sys folders on the first level under the root page (id=0).

root
    sys folder 1 <- level 1
        page a <- level 2
        page j
        page k
    sys folder 2
        page e
        page u
        page o
    sys folder 3
        page p
        page w
        page q
...

Problem:
When we create a new page on level 2 first and set the flag "is_siteroot" afterwards, the slug generates by itself.
i.e.: page title "www.project-abc.com" becomes "/wwwproject-abccom".

An editing afterwards of the slug field is not possible, because it's not visible (see 1_no-slug-field-for-pages-on-level-2.jpg).
We have to change the field manually by accessing the database (see 2_generated-slug.jpg).

If there is no way to edit the field in the backend of Typo3, the root page is not accessible and the slugs of the child pages will have the root slug prepended ("/wwwproject-abccom/about-us").

When we create a page on level 1 the slug will get the value "/", which is correct and the field is visible for editing (see 3_slug-field-visible_for_pages_on_level_1.jpg).

In addition:
The site configurations do exist and work (example: 4_site-configiration-level-2.jpg).


Files


Related issues 4 (1 open3 closed)

Related to TYPO3 Core - Bug #90736: Wrong slug fields for siteroots (level > 1) in multidomain environment and no possibility to modify themNew2020-03-11

Actions
Related to TYPO3 Core - Bug #89311: Flaws in site configuration when creating new page on root-levelRejected2019-09-30

Actions
Has duplicate TYPO3 Core - Bug #89014: Field slug should be editable on page where SiteConfiguration is locatedClosed2019-08-26

Actions
Has duplicate TYPO3 Core - Bug #90932: PseudoSiteTcaDisplayCondition always checks l10n_parentClosed2020-04-02

Actions
Actions #1

Updated by Jan Kornblum over 4 years ago

  • Related to Bug #90736: Wrong slug fields for siteroots (level > 1) in multidomain environment and no possibility to modify them added
Actions #2

Updated by Riccardo De Contardi about 4 years ago

Is this issue still present on 10.4.0-dev (latest master)? Could you add a step-by-step guide on how to reproduce your issue?

With the config shown on my attached file (Schermata 2020-03-29 alle 17.38.57.png) the slug field seems available and editable.

Am I missing something?

Actions #3

Updated by Riccardo De Contardi about 4 years ago

Is this issue related? #89311

Actions #4

Updated by Markus Klein about 4 years ago

  • Related to Bug #89311: Flaws in site configuration when creating new page on root-level added
Actions #5

Updated by Anonymous about 4 years ago

Way to reproduce:
- create a root-page inside a StorageFolder and add a SiteConfiguration
- edit the page
-> the field slug is not visible and so not editable
(this is for the example above)

BUT it works with all types of pages, so:
The "real" error-msg should be

Editing a slug field on a root page (page with SiteConfiguration) is not possible if parent uid of this root page is > 0

So in a project where the root-pages are not on root-level this happens.
Testet with current TYPO3 9.5.15.

Actions #6

Updated by Anonymous about 4 years ago

Found a workaround - maybe this helps to find the main issue..

If you add a SiteConfiguration to the first-level Root-Page (doktype of that page does not metter - can evenbe a folder) then its working also for the subpages.

So in the example above: add a SiteConfig to sys folder 1, sys folder 2, aso. with dummy-bases. The Site-Roots page a, page j, aso will have the slug available again.

Update: the real Error-msg should be:

Editing a slug field on a root page (page with SiteConfiguration) is not possible if parent uid of this root page is > 0 and TreeRoot has no SiteConfiguration. :-)

Actions #7

Updated by Riccardo De Contardi about 4 years ago

  • Related to Bug #89014: Field slug should be editable on page where SiteConfiguration is located added
Actions #8

Updated by Riccardo De Contardi about 4 years ago

  • Status changed from Needs Feedback to New
Actions #9

Updated by Robert Wolle about 4 years ago

  • Subject changed from Wrong "slug" generation of pages on tree level > 1 and possible editing afterwards ("is_siteroot" has no effect) to Editing a slug field on a root page (page with SiteConfiguration) is not possible if parent uid of this root page is > 0 and TreeRoot has no site configuration
Actions #10

Updated by Helmut Hummel almost 4 years ago

  • Related to deleted (Bug #89014: Field slug should be editable on page where SiteConfiguration is located)
Actions #11

Updated by Helmut Hummel almost 4 years ago

  • Has duplicate Bug #89014: Field slug should be editable on page where SiteConfiguration is located added
Actions #12

Updated by Helmut Hummel almost 4 years ago

  • Has duplicate Bug #90932: PseudoSiteTcaDisplayCondition always checks l10n_parent added
Actions #13

Updated by Gerrit Code Review almost 4 years ago

  • Status changed from New to Under Review

Patch set 1 for branch 9.5 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/65066

Actions #14

Updated by Gerrit Code Review almost 4 years ago

Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/65116

Actions #15

Updated by Gerrit Code Review almost 4 years ago

Patch set 1 for branch 10.4 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/65192

Actions #16

Updated by Helmut Hummel almost 4 years ago

  • Status changed from Under Review to Resolved
  • % Done changed from 0 to 100
Actions #17

Updated by Benni Mack over 3 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF