Skip to content
Snippets Groups Projects
  1. Apr 27, 2024
  2. Apr 25, 2024
  3. Apr 24, 2024
    • David Hedden's avatar
      [BUGFIX] Enable multi-level language fallback in extbase · e285595a
      David Hedden authored
      Provide the current language fallback chain to new
      instance of LanguageAspect. So it can be used in PageRepository
      to let extbase records use the fallback chain.
      
      Resolves: #91781
      Releases: main, 12.4
      Change-Id: I291c73c05772533919a7bf6beaa767d156bc9d74
      Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83981
      
      
      Tested-by: default avatarAndreas Kienast <a.fernandez@scripting-base.de>
      Tested-by: default avatarcore-ci <typo3@b13.com>
      Reviewed-by: default avatarAndreas Kienast <a.fernandez@scripting-base.de>
      e285595a
    • Stefan Bürk's avatar
      [BUGFIX] Mitigate invalid exit code for UpgradeWizard without updates · fd76f71a
      Stefan Bürk authored
      Wizards not marked as done, but not having updates, display a
      notice `No changes applied, marking wizard as done.` when using
      the CLI command `bin/typo3 upgrade:run <wizard-identifier>` and
      return an error exit code. This also happen when not specifying
      a single wizard, but running all available ones.
      
      The GUI based upgrade execution behaves different, as it does not
      return an exit code and does not display information about
      `no changes applied`, like its CLI counterpart.
      
      This change:
      
      * Adds new concrete exception classes for the `upgrade:run`
        command.
      
      * Modifies `UpgradeWizardCommand::getUpgradeWizard()` to
        throw now one of the new concrete exception or return a
        wizard instance to run.
      
      * Skips available upgrade wizards not eligible to be executed.
      
      Resolves: #103447
      Releases: main, 12.4
      Change-Id: Ib6eab07919bb2f6e11bac774ecfd333572c2205f
      Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83979
      
      
      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>
      fd76f71a
    • Stefan Bürk's avatar
      [BUGFIX] Use Guzzle request to fetch external error page content · 48b7cc6c
      Stefan Bürk authored
      TYPO3 provides the ability to configure different error handlers for
      specific (or all) error codes, as well as the error handler type
      to use (core handler or custom).
      
      The `\TYPO3\CMS\Core\Error\PageErrorHandler\PageContentErrorHandler`
      allows to specify a target using the link handler. The default config
      allows to define `LinkService::TYPE_PAGE` and `LinkService::TYPE_URL`.
      
      After implementing and stabilizing the TYPO3 sub-request feature,
      this particular error handler has been refactored to use an internal
      sub-request to resolve the error page content: An external URL not
      matching the same instance or having a page unavailable within
      the TYPO3 instance will not return any content.
      
      This change modifies the `PageContentErrorHandler` to send a Guzzle
      request for an external URL instead of using internal sub-requests,
      even if it would access the originating instance again. A limitation
      is that the requested URL **must** return a HTTP status-code 200.
      
      A custom request header is attached to this request. It is then
      checked to avoid recurring errors or loops in the page-resolving
      workflow.
      
      Resolves: #103399
      Related: #98396
      Related: #94402
      Releases: main, 12.4
      Change-Id: If09158abd2aa9246bcb7a4fa41a0ad6e4a0f942c
      Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83978
      
      
      Tested-by: default avatarcore-ci <typo3@b13.com>
      Tested-by: default avatarStefan Bürk <stefan@buerk.tech>
      Reviewed-by: default avatarStefan Bürk <stefan@buerk.tech>
      48b7cc6c
  4. Apr 23, 2024
  5. Apr 22, 2024
  6. Apr 21, 2024
  7. Apr 20, 2024
  8. Apr 19, 2024
  9. Apr 18, 2024
  10. Apr 17, 2024
  11. Apr 16, 2024