1. 17 Aug, 2022 10 commits
  2. 16 Aug, 2022 1 commit
  3. 15 Aug, 2022 2 commits
    • Elias Häußler's avatar
      [BUGFIX] Do not hide ContentObjectRenderer on form rendering · d3d8bc04
      Elias Häußler authored and Oliver Hader's avatar Oliver Hader committed
      With #93887 (respectively #92406), a more convenient rendering
      mechanism for forms was introduced. A new FormRequestHandler
      centralized all the logic from the <formvh:render> view helper
      to allow smoother form handling. However, the new implementation
      used to hide the current ContentObjectRenderer implementation
      and instead always fetched a new instance with
      This no longer allows to determine the current content object
      rendering context from e.g. form finishers. Since the current
      implementation can be retrieved by the ConfigurationManager,
      it is now used in the <formvh:render> view helper, falling
      back to a new ContentObjectRenderer instance in case the
      ConfigurationManager does not actually provide an instance
      of ContentObjectRenderer.
      Resolves: #97977
      Related: #93887
      Related: #92406
      Releases: main, 11.5
      Change-Id: Iabf4e93e6aff8da742321958730521ef1696f130
      Reviewed-on: https://review.typo3.org/c/Packages/TYPO3....
    • Nikita Hovratov's avatar
      [BUGFIX] Correct tree.pagelayout condition evaluation · 0303a9c1
      Nikita Hovratov authored
      With #88276 a new condition has been implemented to check
      for current selected pageLayout in FE and BE, example:
      [tree.pagelayout == "pagets__simple"]
      This has various bugs.
      * The evaluation stops at the sys_template record that has
        'root' flag set. This is not in-line with the backend
        condition implementation, which goes further up in rootline.
      * The evaluation does not look for first specified layout
        up in rootline, but goes from root down to selected page.
        The condition thus calculates wrong layout when different
        'backend_layout_next_level' are nested on rootline pages,
        it picks the uppermost set, not the lowermost one.
      This is fixed by using TSFE->rootLine instead of tmpl->rootLine,
      since TSFE->rootLine provides the full rootline in correct
      * Similar to FE, the evaluation should go up in rootline,
        but is processed downwards instead.
      This is fixed by handing over the 'reversed' full rootline.
      The v12 version of the patch is slightly different: Patch
      for issue #97963 introduced yet another bug by accessing
      TSFE->config['rootLine'], which isn't set at all at this
      point in the frontend processing chain when the page is not
      yet cached, or has no USER_INT or COA_INT.
      Resolves: #98044
      Related: #88276
      Related: #97963
      Releases: main, 11.5
      Change-Id: I1dc9a4dfc6aea6bec4d8e2eb65a6919d486f4a99
      Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/75319
      Tested-by: core-ci's avatarcore-ci <typo3@b13.com>
      Tested-by: Stefan Bürk's avatarStefan Bürk <stefan@buerk.tech>
      Tested-by: Christian Kuhn's avatarChristian Kuhn <lolli@schwarzbu.ch>
      Tested-by: Nikita Hovratov's avatarNikita Hovratov <nikita.h@live.de>
      Reviewed-by: Stefan Bürk's avatarStefan Bürk <stefan@buerk.tech>
      Reviewed-by: Christian Kuhn's avatarChristian Kuhn <lolli@schwarzbu.ch>
      Reviewed-by: Nikita Hovratov's avatarNikita Hovratov <nikita.h@live.de>
  4. 14 Aug, 2022 1 commit
  5. 13 Aug, 2022 1 commit
  6. 12 Aug, 2022 19 commits
  7. 11 Aug, 2022 2 commits
  8. 10 Aug, 2022 4 commits