Project

General

Profile

Actions

Bug #91438

closed

SiteAccessorTrait is too strict, when resolved record is not part of a site

Added by Helmut Hummel almost 4 years ago. Updated almost 4 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2020-05-19
Due date:
% Done:

100%

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

Description

When saving a reocrd on a page that is not part of a site, the slug field of this record,
despite being set to "uniqueInSite" is not checked for uniqueness, as it is assumed unique enough.

The SiteAccessorTrait in contrast to that, declares such record not part of the current site.

Both parts though must always behave the same and make the same assumptions.

In the future, we should throw a warning or at least a notice for such case. Records with slugs defined as "uniqueInSite"
must never be stored outside a site. It does not make any sense to do so.
Instead configuration needs to be adapted to either "unique" or even empty, whatever fits the use case.


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #91235: News Detail Page 404 after upgrade 9.5.16Closed2020-04-29

Actions
Actions

Also available in: Atom PDF