Skip to content
Snippets Groups Projects
  1. Jul 27, 2023
  2. Jul 26, 2023
  3. Jul 25, 2023
  4. Jul 24, 2023
  5. Jul 21, 2023
  6. Jul 19, 2023
  7. Jul 18, 2023
    • Nikita Hovratov's avatar
      [BUGFIX] Fix fallback icons for custom page types · ea45fb45
      Nikita Hovratov authored
      Since the introduction of customizable page type icons,
      the fallback icons did no longer work. Only the icon
      and variations for "contentFromPid" worked. The reason
      is, that these icons are prefixed with "page" while the
      other ones are prefixed with the doktype ("1").
      
      This is fixed now by providing an optional argument
      for the getRecordTypeForPageType method, which takes
      the type name as parameter. The default is "1".
      
      Resolves: #101379
      Related: #90042
      Releases: main, 12.4, 11.5
      Change-Id: Ia4379899642ad477026dd73b1ac0c22b918a1629
      Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/80059
      
      
      Tested-by: default avatarcore-ci <typo3@b13.com>
      Tested-by: default avatarNikita Hovratov <nikita.h@live.de>
      Reviewed-by: default avatarNikita Hovratov <nikita.h@live.de>
      ea45fb45
    • Stefan Bürk's avatar
      [BUGFIX] Prevent reaching the placeholder limit in `indexed_search` · 77433946
      Stefan Bürk authored
      The main query execution builds a QueryBuilder instance out of
      different sub information. Additionally, several hooks can be
      used to influence the created query. On top of this, different
      type of search queries are possible.
      
      This change avoid consuming a lot of placeholder for list based
      `in()` expressions by using a corresponding QueryBuilder method
      suitable for the value type. This means that no placeholder are
      used any longer for list expressions.
      
      Note: Max query size may still be exceeded if the lists would
            getting bigger. This can be adjusted by database server
            administrators, but will lead to another exception for
            really large value lists.
      
      Resolves: #86859
      Releases: main, 12.4, 11.5
      Change-Id: Ic0ac51c13cb74a058d71152ad626c484f696b176
      Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/80080
      
      
      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>
      77433946
    • Stefan Bürk's avatar
      [BUGFIX] Enhance matching order for regex based redirects · 1f1082b9
      Stefan Bürk authored
      RegEx redirects have been processed in the order how they
      have been inserted into the database ignoring the flag
      `respect_query_parameters` completely. Due to this fact,
      a non-query argument based regex redirect would match
      before a concrete query-argument aware regexp redirect
      have been matched - additionally favored by the changes
      introduced with #96480 to provide a fallback.
      
      To combine all use-cases and additionally fix the detected
      issues, this change now splits the cached regex redirects
      into two flavors:
      
      * `regexp_respect_query_parameters`
      * `regexp_flat`
      
      That follows the pre-selection for the non-regex redirects.
      Redirects respecting query paramaters have higher precedence
      above the non-respecting once. Therefore, the matching flow
      in the `RedirectService` has been aligned correspondingly to
      respect this separated workflow.
      
      The #96480 is now only applied for regex redirects which do
      not respect query-arguments at all. It should be considered
      if we should remove that safety fallback and enforce correct
      regex redirects in a dedicated future change.
      
      Furthermore, a deterministic sorting criteria chain has been
      added to the `RedirectCacheService` to ensure a deterministic
      loading and caching order of redirects.
      
      The changes play together, which is the reason why they are
      included in one change and to avoid a inbetween incorrect
      test chain.
      
      Regression tests have been added to cover the cases.
      
      Resolves: #101191
      Related: #96480
      Releases: main, 12.4, 11.5
      Change-Id: I9638835c33809e92ba883efb65d86bb1e9f5031b
      Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/80079
      
      
      Tested-by: default avatarStefan B�rk <stefan@buerk.tech>
      Reviewed-by: default avatarStefan B�rk <stefan@buerk.tech>
      Tested-by: default avatarcore-ci <typo3@b13.com>
      1f1082b9
    • Andreas Fernandez's avatar
      [BUGFIX] Make icon cache in localStorage version-aware · 2bc1c01d
      Andreas Fernandez authored
      The identifier for the icon cache used in the client's localStorage is
      now version-aware to get a chance of updated icons after a release. It
      now uses the same identifier as the backend cache.
      
      Previously, only the registry state itself was taken into account which
      may not change if icons assets get updated.
      
      Resolves: #101348
      Releases: main, 12.4, 11.5
      Change-Id: I15dfc9d4bf1288f9787f88f579beccf3b13a3fc6
      Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/80073
      
      
      Tested-by: default avatarBenjamin Franzke <ben@bnf.dev>
      Tested-by: default avatarcore-ci <typo3@b13.com>
      Reviewed-by: default avatarBenjamin Franzke <ben@bnf.dev>
      2bc1c01d
  8. Jul 17, 2023
  9. Jul 15, 2023
  10. Jul 14, 2023
  11. Jul 13, 2023
  12. Jul 12, 2023
  13. Jul 11, 2023
  14. Jul 10, 2023
  15. Jul 08, 2023