Task #85938

Epic #84726: Initiative: URL Routing Integration / Site Handling

Epic #84728: Introduce speaking URLs for pages

Epic #84729: Implement "slug" handling for pages and other records

Handle renaming of "base" property of a site

Added by Oliver Hader 11 months ago. Updated 10 months ago.

Status:
Rejected
Priority:
Should have
Assignee:
-
Category:
Link Handling, Site Handling & Routing
Target version:
Start date:
2018-08-23
Due date:
% Done:

0%

TYPO3 Version:
9
PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

Renaming the "base" property can happen via file-system (YAML file) or using the backend user interface of the "sites" module.
Changing the "base" property results in different URLs for all nested pages (or slugs in general). This should result in having redirects being created automatically (or based on a user confirmation dialog - which is not possible if YAML file has been modified directly).

History

#1 Updated by Benni Mack 11 months ago

don't know if this fixable / detectable.

Same goes if somebody adds a "is_siteroot" checkbox - this might mess up everything.

#2 Updated by Susanne Moog 11 months ago

  • Category set to Link Handling, Site Handling & Routing

#3 Updated by Susanne Moog 11 months ago

  • Status changed from New to Accepted

#4 Updated by Frank Naegler 10 months ago

I would opt for a read-only field with a hint why this field is read only (after first save) as a first step.
Adding an info why you should not change the base and what steps must be done in case you really want change the base.
This list could later be used to build a kind of upgrade wizard to change the base in the backend.

#5 Updated by Susanne Moog 10 months ago

  • Status changed from Accepted to Rejected

After short discussion with Benni rejected for now.

Also available in: Atom PDF