Project

General

Profile

Actions

Bug #86195

closed

Localization of page fails because of SiteNotFoundException

Added by Andreas Kienast about 6 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
Site Handling, Site Sets & Routing
Start date:
2018-09-07
Due date:
% Done:

100%

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

Description

Given scenario:

Have a root page (is_siteroot = 1) with site configuration and localization to Dansk. On the same level, create a new page without setting the is_siteroot flag. When attempting a localization on that page to Dansk as well, the exception is thrown:

(1/1) SiteNotFoundException
No pseudo-site found in root line of page XXX

The REAL interesting thing is, that the reported page XXX is the successfully localized one.


Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Bug #86625: "No pseudo-site found in root line of page" when executing upgrade wizardClosed2018-10-11

Actions
Related to TYPO3 Core - Bug #86809: Resolve strict type assertion in RecordStateFactoryClosed2018-10-31

Actions
Actions #1

Updated by Andreas Kienast about 6 years ago

How I understand the issue:

The failing part is SlugHelper::isUniqueInSite(), the method tries to find a page on the pid of the created localization. Since there is already a localization on the same pid (but on a different "origin"), the wrong records get fetched and thus the code fails.

Actions #2

Updated by Gerrit Code Review about 6 years ago

  • Status changed from New to Under Review

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/58224

Actions #3

Updated by Anja Leichsenring about 6 years ago

how to reproduce:

- have one rootpage [1] with a site configuration
- have another rootpage [2] without a site configuration (just tested, also fails if a site config exists here)
- on [2], have a translation in language {1} => this gets pid [3]
- configure the site configuration on [1] to contain {1}
- go to page module on language view.
- initiate translation of [1] into {1}

=> SiteNotFoundException
No pseudo-site found in root line of page 3.

So the site finder aims for that translated page from [2], where a translation of [1] should be created.

Actions #4

Updated by Anja Leichsenring about 6 years ago

  • Status changed from Under Review to Accepted
Actions #5

Updated by Gerrit Code Review about 6 years ago

  • Status changed from Accepted to Under Review

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

Actions #6

Updated by Gerrit Code Review about 6 years ago

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

Actions #7

Updated by Gerrit Code Review about 6 years ago

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

Actions #8

Updated by Gerrit Code Review about 6 years ago

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

Actions #9

Updated by Gerrit Code Review about 6 years ago

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

Actions #10

Updated by Benni Mack about 6 years ago

  • Target version changed from 9 LTS to Candidate for patchlevel
Actions #11

Updated by Tymoteusz Motylewski about 6 years ago

  • Related to Bug #86625: "No pseudo-site found in root line of page" when executing upgrade wizard added
Actions #12

Updated by Oliver Hader about 6 years ago

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

Updated by Oliver Hader about 6 years ago

  • Related to Bug #86809: Resolve strict type assertion in RecordStateFactory added
Actions #14

Updated by Benni Mack over 5 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF