Bug #86195
closed
Localization of page fails because of SiteNotFoundException
Added by Andreas Kienast about 6 years ago.
Updated over 5 years ago.
Category:
Site Handling, Site Sets & Routing
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.
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.
- Status changed from New to Under Review
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.
- Status changed from Under Review to Accepted
- Status changed from Accepted to Under Review
- Target version changed from 9 LTS to Candidate for patchlevel
- Related to Bug #86625: "No pseudo-site found in root line of page" when executing upgrade wizard added
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
- Related to Bug #86809: Resolve strict type assertion in RecordStateFactory added
- Status changed from Resolved to Closed
Also available in: Atom
PDF