Pseudo Sites a.k.a. "Legacy Sites" are site objects that do not have a configuration yet, but should be treated in various places like a site object, e.g. when finding what kind of languages are available in a pagetree.
[FEATURE] Add "Pseudo" Site functionality
All pages on rootlevel or with "is-siteroot" need
to have a site object as well, but populated
by sys_domain (optional) and all available sys_language
However, this information needs to be compiled
within an entity called "PseudoSite".
This way, the page-based routing ("slug handling")
can use the functionality to detect the uniqueness
of a slug within a page tree.
The routing of sites is moved to a "SiteMatcher" API
class, returning all found information on a request
for a site, also encapsulating the Symfony/Routing
component in there.
This would be exactly the step where further information
about a URL will then be resolved.
Next steps are the usage of Sites and PseudoSites
in TYPO3 Backend, allowing to only show e.g.
languages that are configured, which can be done
Tested-by: TYPO3com <email@example.com>
Reviewed-by: Georg Ringer <firstname.lastname@example.org>
Tested-by: Georg Ringer <email@example.com>
Reviewed-by: Wouter Wolters <firstname.lastname@example.org>
Tested-by: Wouter Wolters <email@example.com>