Epic #84727

Epic #84726: Initiative: URL Routing Integration / Site Handling

Site Handling - Part 2 / Missing Pieces

Added by Benni Mack over 1 year ago. Updated about 1 year ago.

Status:
Closed
Priority:
Should have
Assignee:
Category:
Link Handling, Site Handling & Routing
Target version:
Start date:
2018-04-17
Due date:
% Done:

100%

Sprint Focus:

Description

1. We need to resolve the introduced @todos in the initial commit

2. Add tests for the new APIs

3. Create test cases for 1000 sites and find the performance bottlenecks

4. Create an API to fetch all language objects for a page and use that in the BE to encapsulate all calls to sys_language. Also encapsulate this for the TSconfig option for defining the "default language" options in TSconfig.

5. After 4 - go through page module, list module, view module and use site handling in there

6. Make rootline resolving better / faster (question is: how)

7. Allow to make a site configuration "read-only" and respect that on a per-

8. Add TypoScript conditions [site = site-identifier], and [siteLanguage = de-DE] (no languageId please!)

Discussion points.
- How should we consider pages with "non-sites"? Convert non-sites to pseudo-site? having sys_domain as fallback?
- How to handle schema- and domain-less bases? "/site1" and "/site2" are valid sites - especially when it comes to nesting
- How to handle http+https in a site base?
- How to handle multiple domains in one site? placeholders?
- How to handle "is_siteroot"? Upgrade wizard to give all root-level pages "is_siteroot"?
- How to deal with storage folders that are not within a site?
- How to handle record translations in page/list module which are there but not available for the current site setup?
- How to handle a new language which should not show up yet on the live setup (yet)?
- How to handle language fallbacks properly for content records (what should we allow, and how to implement this?)


Subtasks

Feature #84760: Conditions for site languageClosedGeorg Ringer

Task #85143: Improve deleting site configurationsClosed

Task #85163: Allow site handling with non-absolute URLs like "/"Closed

Task #85164: Allow to only show site languages in BE ("enabledInFrontend")Closed

Task #85165: Allow to accept https and http as incoming, and optional redirectsClosed

Task #85166: Add tests for a frontend rendering based on sitesClosed

Task #85812: Throw PSR-7 Responses up to ApplicationClosed

Task #85813: Add frontend functional tests for site handlingClosed

Task #85820: Add more tests to nested domains and langaugesClosedBenni Mack

Task #85897: Streamline site handling functional testsClosedBenni Mack

Task #85941: Reduce amount of executed functional frontend testsClosedOliver Hader

Task #85962: Add frontend functional tests for pages having slugsClosed

Task #85717: Add site interfaceClosed

Task #85719: Make base detection more robustClosed

Bug #85819: Exception on non-existing error handlerClosedBenni Mack

Task #85887: Optimize language labels in IRRE titleClosedFrank Naegler

Task #85892: Centralize sys_domain resolvingClosedBenni Mack

Task #85900: Introduce Pseudo SitesClosedBenni Mack

Task #85919: Flush site caches if sys_domain or sys_language was modifiedClosedBenni Mack

Task #85929: Move error handler constants to SiteInterfaceRejected

Task #85930: Add API for Site resolvingClosedBenni Mack

Bug #85950: Preview URL in backend is invalidRejected

Task #85951: Move domainStartPage setting to PageResolverClosedBenni Mack

Task #85954: Move Site Resolving before TSFE initialization in FrontendRejectedBenni Mack

Bug #86011: Site Configuration Module should show hidden languagesClosedBenni Mack

Task #86027: Change Site Base Handling to PSR-7 URI InterfaceClosedBenni Mack

Bug #86078: Not localized labels in site moduleClosedGeorg Ringer

History

#1 Updated by Benni Mack over 1 year ago

  • Target version changed from 9.3 to 9.4

#2 Updated by Benni Mack over 1 year ago

Left over:

- "Pseudo-Sites" - Create an API to fetch all language objects for a page and use that in the BE to encapsulate all calls to sys_language. Also encapsulate this for the TSconfig option for defining the "default language" options in TSconfig.
- go through page module, list module, view module and use site handling in there
- Allow to make a site configuration "read-only" and respect that on a per-site basis.

Discussion points.
- How to handle multiple domains in one site? placeholders?
- How to handle "is_siteroot"? Upgrade wizard to give all root-level pages "is_siteroot"?
- How to handle record translations in page/list module which are there but not available for the current site setup?
- How to handle a new language which should not show up yet on the live setup (yet)?

#3 Updated by Benni Mack about 1 year ago

Left over:
- Allow to make a site configuration "read-only" and respect that on a per-site basis.
- Introduce one API for resolving Sites + Pseudo Sites
- Introduce "NullSite" entity.

Discussion points.
- How to handle multiple domains in one site? placeholders? Pseudo-Sites is solved, but not for page roots with site configuration.

#4 Updated by Susanne Moog about 1 year ago

  • Target version changed from 9.4 to 9 LTS

#5 Updated by Susanne Moog about 1 year ago

  • Status changed from New to Accepted

#6 Updated by Susanne Moog about 1 year ago

  • Status changed from Accepted to In Progress

#7 Updated by Benni Mack about 1 year ago

  • Status changed from In Progress to Closed

Also available in: Atom PDF