Skip to content
Snippets Groups Projects
  1. Apr 21, 2024
    • Stefan Bürk's avatar
      [BUGFIX] Ensure that relative target link can be set in EXT:redirects · 2f234688
      Stefan Bürk authored
      The TYPO3 system extension `redirects` now fully supports the setting
      of relative links as the `target` URL, which is a documented feature.
      
      Previously, an issue arose when attempting to use path links with
      leading slashes as URLs. This issue has been addressed in #101083,
      marking the initial step toward resolving the problem of relative
      target links.
      
      Additionally, the fix now allows for linking to arbitrary resources,
      even those that do not currently exist in the File Abstraction Layer
      (FAL).
      
      The class `TYPO3\CMS\Core\LinkHandling\LegacyLinkNotationConverter`
      has been changed to limit the handling of arbitrary resources
      to the smallest scope to reuse existing code and to use them
      as `LinkService::TYPE_URL` links.
      
      The superflous outer catch block has been removed to remove
      dead code. In addition, a test for coverage has been added
      that covers DataHandler and the lower LinkHandling layer.
      
      Resolves: #103387
      Related: #101083
      Releases: main, 12.4
      Change-Id: I51cad29e5551824a0ad8d4528aa43cff7e0f9da7
      Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83946
      
      
      Tested-by: default avatarcore-ci <typo3@b13.com>
      Reviewed-by: default avatarStefan Bürk <stefan@buerk.tech>
      Tested-by: default avatarStefan Bürk <stefan@buerk.tech>
      2f234688
  2. Apr 20, 2024
  3. Apr 19, 2024
  4. Apr 18, 2024
  5. Apr 17, 2024
  6. Apr 16, 2024
  7. Apr 15, 2024
  8. Apr 13, 2024
  9. Apr 12, 2024
  10. Apr 11, 2024
  11. Apr 10, 2024
  12. Apr 09, 2024
  13. Apr 08, 2024
    • Stefan Bürk's avatar
      [TASK] Add additional tests for `RedirectService` handling · e82170f2
      Stefan Bürk authored
      This change adds additional tests to cover additional
      variants for `EXT:redirects` handling. Placing guards
      helps to avoid mitigating regressions for these cases.
      
      Resolves: #103564
      Related: #103395
      Related: #103555
      Releases: main, 12.4
      Change-Id: I4b6deb258610d1a3d416c16eec610aa2bfd9ef72
      Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83665
      
      
      Tested-by: default avatarStefan Bürk <stefan@buerk.tech>
      Tested-by: default avatarcore-ci <typo3@b13.com>
      Reviewed-by: default avatarStefan Bürk <stefan@buerk.tech>
      e82170f2
    • Stefan Bürk's avatar
      [BUGFIX] Avoid `NullSite` in `Request` object setup in RedirectService · 1a1ff716
      Stefan Bürk authored
      Redirects can match even if no SiteConfiguration could
      be determined for the current request and a `NullSite`
      has been added as request attribute. In this case, the
      `RedirectService` already resolves a SiteConfiguration
      for the matched redirect.
      
      Bootstrapping a  `TypoScriptFrontendController` is done
      using the resolved SiteConfiguration, still using the
      NullSite in the request for id determination and loading
      TypoScript.
      
      In cases where no real `sys_template` records exists,
      for example when `b13/bolt` is used to provide fake
      rows, it is important to avoid NullSite.
      
      This change uses the redirect target based resolved
      site in case the request does not contain a valid
      site object. Prepared test from #103555 is enabled
      now to guard this case for the future.
      
      Note: TYPO3 v13 recieved quite some refactoring in
      the Middleware, TSFE and TypoScript loading order
      a long with a factory and fixed this already. This
      is a simple solution for TYPO...
      1a1ff716