Skip to content
Snippets Groups Projects
  1. Apr 08, 2024
  2. Apr 07, 2024
    • Stefan Bürk's avatar
      [TASK] Add `RedirectService` tests as preparation for a bugfix · ad2f507c
      Stefan Bürk authored
      Issue with the `RedirectService` has been reported
      wiht #103395 related to non-matching SiteConfig in
      cases no TypoScript template records exists, like
      when `b13/bolt` is used in instances.
      
      Changes #103437, #103439 and #103554 fixed the
      mentioned issue #103395 for TYPO3 v13, leaving
      the issue open for TYPO3 v12.
      
      Note: For v12 the regression test dataset needs
      to be disabled for now, and will be enabled with
      the upcoming fix.
      
      This change adds now some tests for non matching
      SiteConfiguration for `source_hosts`.
      
      Resolves: #103555
      Related: #103395
      Related: #103554
      Related: #103439
      Related: #103437
      Releases: main, 12.4
      Change-Id: I2c72de3fa5f8d8aae5e6d2ca702ea4685cd367b3
      Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83695
      
      
      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>
      ad2f507c
    • Lukas Maxheim's avatar
      [BUGFIX] Create backend users via CLI respects TCA default options · 7279f635
      Lukas Maxheim authored
      This change introduces the use of the DataHandler instead of the
      QueryBuilder when creating backend users via CLI command
      `backend:user:create`.
      
      This ensures that the user is initialized with TCA default options and
      the creation and history of the new user is logged to the TYPO3 log.
      
      Resolves: #102062
      Releases: main, 12.4
      Change-Id: I78f7093108d1df3c6d37ab7545911365d3c846bb
      Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83688
      
      
      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>
      7279f635
    • Andreas Kienast's avatar
      [BUGFIX] t3editor: Keep original flex configuration · a1edae03
      Andreas Kienast authored
      When t3editor got streamlined in the past, configuration for flex was
      defined that conflicts with CodeMirror's internal style definition,
      leading to UI glitches like "cut out" content, see screenshot attached
      to the ticket..
      
      This commit removes the conflicting CSS.
      
      Resolves: #101442
      Releases: main, 12.4
      Change-Id: Ie5b9f8d498cdaef0b3455e05e247cb5fd64b0617
      Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83685
      
      
      Tested-by: default avatarAndreas Kienast <a.fernandez@scripting-base.de>
      Reviewed-by: default avatarAndreas Kienast <a.fernandez@scripting-base.de>
      Tested-by: default avatarcore-ci <typo3@b13.com>
      a1edae03
    • Markus Klein's avatar
      [BUGFIX] Use correct timezones with timestamp based \DateTime · 57dcbe82
      Markus Klein authored
      As documented by PHP, `\DateTime` or `\DateTimeImmutable`
      objects created with a timestamp only ('@12345678') as the
      first constructor argument will use UTC as TimeZone.
      
      Creating an object instance without any constructor arguments
      will use the `date_default_timezone_get()` timezone for the
      object - and setting the timestamp using `setTimestamp()` will
      not change the object's timezone.
      
      That means, that formatting the value will be done using
      the object Timezone and **NOT** the default PHP Timezone
      (`date_default_timezone_get()`).
      
      Consequently, this may lead to wrong interpretation of
      the displayed formatted value in the context of another
      timezone - if no timezone information (+0000/-0100) is
      included.
      
      This change streamlines this for a couple of places were
      it is expected to format date, datetime or time values
      for the current context timezone by ensuring objects get
      the current timezone set instead of `UTC`.
      
      Note: Changing the date defau...
      57dcbe82
    • Christian Kuhn's avatar
      [BUGFIX] Mitigate misusing request 'id' as pages-uid in extbase BE · 524267cd
      Christian Kuhn authored
      The backend uses request GET/POST parameter 'id' as convention for
      "pages uid" at various places: Especially the BackendModuleValidator
      checks for this parameter early, to deny access to pages a BE user
      has no access to.
      
      This convention is a broken misuse: There is no such convention,
      and for instance the filelist module uses 'id' to transfer a
      selected "storage-uid:path".
      
      The BackendModuleValidator mitigates this by calling
      MU::canBeInterpretedAsInteger() before interpreting that
      parameter as a pages-uid.
      
      The extbase BackendConfigurationManager also uses 'id' to retrieve
      the FE TypoScript configuration for this "pages-uid", it however
      does not check with MU::canBeInterpretedAsInteger(), first.
      
      The patch adds a MU::canBeInterpretedAsInteger() check to extbase
      BackendConfigurationManager to be in-line with BackendModuleValidator,
      and adds `@todo` comments outlining the general misuse of the argument.
      
      Change-Id: I9b53a521bde4d3c145bfda2994d81dc4abf9c103
      Resolves: #103540
      Related: #96797
      Releases: main, 12.4
      Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83678
      
      
      Reviewed-by: default avatarChristian Kuhn <lolli@schwarzbu.ch>
      Tested-by: default avatarcore-ci <typo3@b13.com>
      Tested-by: default avatarChristian Kuhn <lolli@schwarzbu.ch>
      524267cd
  3. Apr 05, 2024
  4. Apr 04, 2024
  5. Apr 03, 2024
  6. Apr 02, 2024
  7. Apr 01, 2024
  8. Mar 25, 2024
  9. Mar 23, 2024
  10. Mar 22, 2024
  11. Mar 21, 2024
  12. Mar 20, 2024
  13. Mar 19, 2024
  14. Mar 18, 2024