Feature #86216

Allow empty slug for root pages and sysfolders

Added by Georg Tiefenbrunn 9 days ago. Updated 1 day ago.

Status:
Needs Feedback
Priority:
Should have
Assignee:
-
Category:
Link Handling, Site Handling & Routing
Target version:
Start date:
2018-09-10
Due date:
% Done:

0%

PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

Consider following page tree (TYPO3 CMS 9.4 composer):

TYPO3 [0]
+ Root [1]
  + General Storage [2]
    + News [3]
    + ...
  + Websites [4]
    + Website 1 [5]
      + Folder [6]
        + Imprint [7]
    + Website 2 [8]
  • Page Root [1] has a domain record 'typo3.example.org' to provide one easy entry point for the CMS instance. It's an external link to '/typo3'.
  • News records are stored in Root > General Storage > News [3] (e.g. no need for news authors to see 'Websites')
  • Pages Website 1 [5] and Website 2 [8] have both is_siteroot=1 and a valid site configuration

I'm missing RealURL's 'Exclude from Speaking URL' setting:

Empty slug for root pages

Pages Website 1 [5] and Website 2 [8] can't have slug=/. Saving slug=/ results e.g. in slug=/1. Recalculating the slug will produce slug=/websites/{pageName}.

As an Integrator/Editor it should be possible to create "base slugs" (slug=/ ) for pages with is_siteroot=1.

Empty slug for sysfolders

To e.g. exclude pages from the main nav menu but include it them in some other menu (e.g. 'legal links') and keep a short URL page Imprint [7] is placed inside Folder [6].

As an Integrator/Editor it should be possible to create "empty slugs" (slug=/ ) for sysfolders.


Related issues

Related to TYPO3 Core - Epic #84728: Introduce speaking URLs for pages In Progress 2018-08-22

History

#1 Updated by Georg Tiefenbrunn 9 days ago

  • Related to Epic #84728: Introduce speaking URLs for pages added

#2 Updated by Georg Ringer 7 days ago

  • Status changed from New to Needs Feedback

You know that you can edit the full slug and change it for the imprint directory to /imprint?

Having empty slugs is a bad idea as it creates other problems like what if you change a sysfolder to a page again and vice versa?

Is it fine to close the issue?

#3 Updated by Georg Tiefenbrunn 5 days ago

Georg Ringer wrote:

You know that you can edit the full slug and change it for the imprint directory to /imprint?

Yes. But please consider the following from an editor's view:

With RealURL's 'Exclude from Speaking URL' setting

  • Apply 'Exclude from Speaking URL' to Folder [6]
  • Put all pages which should be included in main menu inside Website 1 [5]
  • Put all pages which should no be included in main menu inside Folder [6]
Result:
  • All subpages of Folder [6] will be available via /slug without further configuration
  • All subpages of Folder [6] won't be included in main menu without further configuration

V9 slugs

  • You have to manually edit the /slug for all subpages of Folder [6]

#4 Updated by Georg Tiefenbrunn 5 days ago

Georg Ringer wrote:

Having empty slugs is a bad idea as it creates other problems like what if you change a sysfolder to a page again and vice versa?

TL;DR: Website root pages (is_siteroot=1) should have slug=/ regardless of pages.pid

The more important part is slug generation for website root pages (is_siteroot=1) which are not direct children of TYPO3 [0].

One of the key features of TYPO3 is its ability to handle multi site and multi domain instances. With the current slug creation we are forced to place website root pages below TYPO3 [0] (= I found no other way than to place all website root pages below TYPO3 [0]. As soon as they are placed inside a sysfolder the slug of this folder will be added to all page slugs).

My way of implementing multi domain instances which mostly share a lot of non page related stuff as news, events, addresses, etc. is to use the above described structure:

  • Put all Websites into a sysfolder (Websites [4]) and assign only one db mount to users which may edit pages/page content.
  • Put all non-page related records in a sysfolder (General Storage [2])

Using this method all users have the same page tree (with branches corresponding to their user rights). Admin and power users can quickly close all page related stuff by closing the Websites [4] subfolder.

#5 Updated by Susanne Moog 1 day ago

  • Category set to Link Handling, Site Handling & Routing

Also available in: Atom PDF