[BUGFIX] Loosen site check for records not stored in site context

When saving a record 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.

This assumption needs to be applied as well when resolving
the record, instead of assuming the resolved record is not part
of the current site.

Releases: master, 9.5
Resolves: #91438
Change-Id: I347909b9b4caa523de3ad8e5d84c465e5d57b052
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64520


Reviewed-by: Benni Mack <benni@typo3.org>
Reviewed-by: Oliver Hader <oliver.hader@typo3.org>
Tested-by: TYPO3com <noreply@typo3.com>
Tested-by: Oliver Hader <oliver.hader@typo3.org>

typo3/sysext/core/Classes/DataHandling/SlugHelper.php

@@ -303,6 +303,9 @@ class SlugHelper
             $siteOfCurrentRecord = $siteFinder->getSiteByPageId($pageId);
         } catch (SiteNotFoundException $e) {
             // Not within a site, so nothing to do
+            // TODO: Rather than silently ignoring this misconfiguration,
+            // a warning should be thrown here, or maybe even let the
+            // exception bubble up and catch it in places that uses this API
             return true;
         }
         foreach ($records as $record) {

typo3/sysext/core/Classes/Routing/Aspect/SiteAccessorTrait.php

@@ -95,7 +95,11 @@ trait SiteAccessorTrait
             $expectedSite = $this->getSiteMatcher()->matchByPageId($pageId);
             return $expectedSite->getRootPageId() === $this->site->getRootPageId();
         } catch (SiteNotFoundException $exception) {
-            return false;
+            // Same as in \TYPO3\CMS\Core\DataHandling\SlugHelper::isUniqueInSite
+            // where it is assumed that a record, that is not in site context,
+            // but still configured uniqueInSite is unique. We therefore must assume
+            // the resolved record to be rightfully part of the current site.
+            return true;
         }
     }