This project is mirrored from Pull mirroring failed .
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer.
Last successful update .
  1. 21 Dec, 2020 1 commit
    • Benjamin Franzke's avatar
      [TASK] Update bootstrap javascript to 5.0.0-beta1 · 27881b60
      Benjamin Franzke authored and Benni Mack's avatar Benni Mack committed
      Bootstrap v5 – introduced in #92616 – was added with CCS from beta1 but
      JavaScript from alpha2. bootstrap.bundle.js was manually wrapped
      into a AMD closure, and because bootstrap 5.0.0-beta1 contains alot of
      changes regarding data tags, it couldn't be updated in the initial
      Bootstrap is now bundled using rollup using the ES6 sources in order
      to allow for automatic updates through `grunt build`.
      popperjs – previously bundled into bootstrap distributed files –
      is now added as dependency. The bootstap ES6 sources, that we now use
      through rollup, do not bundle this external dependency (for good reasons).
      Dependency added with:
         yarn add @popperjs/core
      Further adaptions contained in this change to ensure beta1 compatibility:
      a) Carousel "item" to "carousel-item" class migration
      b) $.fn.modal(options) does no longer imply $.fn.modal('show')
      c) Fix panels, both JS and CSS (card-group can't be used here)
      d) All bootstrap data- tags are migrated to data-bs-.
         Migrated with
         # renderes a sed substition with the help of a nested sed from all the
         # data-bs attributes that where changed in the twbs/bootstrap commit
         git grep -l data- | xargs sed -i $( \
              curl -s \
     | \
              sed 's/data-bs-[a-z-]*/\n&\n/g' | grep "data-bs-[a-z-]" | \
              sort | uniq | \
              sed 's/data-bs-\(.*\)\([^a-z-]\|$\)/ -e s\/data-\1\\\([^a-z-]\\\)\/data-bs-\1\\1\/g -e s\/data('"'"'\1'"'"')\/data('"'"'bs-\1'"'"')\/g/g' \
         # Revert false positives from the above auto-replacement
         git checkout -- typo3/sysext/core/Documentation/Changelog/ \
              typo3/sysext/backend/Classes/Form/Container/FlexFormContainerContainer.php \
              Build/Sources/TypeScript/backend/Resources/Public/TypeScript/LiveSearch.ts \
              Build/Sources/TypeScript/backend/Resources/Public/TypeScript/FormEngineFlexForm.ts \
              Build/Sources/TypeScript/install/Resources/Public/TypeScript/Module/Settings/ExtensionConfiguration.ts \
         (cd Build && grunt build)
      Resolves: #93126
      Resolves: #93123
      Resolves: #93132
      Related: #92616
      Releases: master
      Change-Id: Ie194d0f87d2c60df7b9e8a6de4893cfaaea55356
      Tested-by: default avatarTYPO3com <>
      Tested-by: default avatarMartin Kutschker <>
      Tested-by: Christian Kuhn's avatarChristian Kuhn <>
      Tested-by: Benni Mack's avatarBenni Mack <>
      Reviewed-by: default avatarMartin Kutschker <>
      Reviewed-by: Christian Kuhn's avatarChristian Kuhn <>
      Reviewed-by: Benni Mack's avatarBenni Mack <>
  2. 20 Dec, 2020 1 commit
    • Matthias Stegmann's avatar
      [FEATURE] Introduce Bootstrap v5 for TYPO3 Backend · 793fc121
      Matthias Stegmann authored and Benni Mack's avatar Benni Mack committed
      This changes removes the frontend framework
      Bootstrap 3, and adds Bootstrap 5 beta 1 (we
      expect Bootstrap 5 final by the time we release TYPO3 v11 LTS).
      Bootstrap v3 is not supported by the Bootstrap
      team any longer, so an update is critical for TYPO3 Core.
      Bootstrap v5 adds a few accessibility improvements
      as well as flexbox for rendering
      containers and grids throughout TYPO3 Backend.
      All JS components are not bound to jQuery anymore,
      and have been reworked.
      A lot of HTML/CSS changes happened, which we
      slowly migrate (and not in a huge change)
      to TYPO3's templates, in order to keep
      this change managable.
      A legacy CSS/SCSS file is added to
      keep some backwards-compatibility classes
      to ease the migration for extension developers
      who have built their own backend modules.
      Key features of Bootstrap 5:
      * "rem" instead of "px" is used by default
      * CSS variables are introduced
      * Improved bootstrap focus outline styling (buttons / inputs / links)
      * Simplified grid functionality
      * use new button color mixin to increase contrast:
        Primary, Success and Warning Button color is now dark instead of white
      EXT:styleguide was used as a basis for
      upgrading to keep compatibility as much
      as possible, but more changes will be coming
      in the next few minor releases.
      Resolves: #92616
      Releases: master
      Change-Id: Iec989f39649b5460b055ec879199faf38e424f2b
      Tested-by: default avatarTYPO3com <>
      Tested-by: Benjamin Franzke's avatarBenjamin Franzke <>
      Tested-by: Oliver Hader's avatarOliver Hader <>
      Tested-by: Oliver Bartsch's avatarOliver Bartsch <>
      Tested-by: Benni Mack's avatarBenni Mack <>
      Reviewed-by: Benjamin Franzke's avatarBenjamin Franzke <>
      Reviewed-by: Oliver Hader's avatarOliver Hader <>
      Reviewed-by: Oliver Bartsch's avatarOliver Bartsch <>
      Reviewed-by: Benni Mack's avatarBenni Mack <>
  3. 22 Oct, 2020 1 commit
  4. 15 Apr, 2020 1 commit
  5. 14 Apr, 2020 2 commits
  6. 02 Apr, 2020 1 commit
  7. 15 Mar, 2020 2 commits
  8. 13 Feb, 2020 1 commit
  9. 29 Jul, 2019 1 commit
  10. 15 Mar, 2019 1 commit
  11. 17 Jan, 2019 1 commit
  12. 01 Oct, 2018 1 commit
  13. 30 Sep, 2018 1 commit
  14. 02 Sep, 2018 1 commit
  15. 27 Aug, 2018 1 commit
  16. 16 May, 2018 1 commit
    • Christian Kuhn's avatar
      [TASK] Streamline TSconfig API · 45c582a8
      Christian Kuhn authored
      Final patch to de-mess the user / page TSconfig related API.
      Page TSconfig can be overriden in user TSconfig by prefixing the
      path with 'page.' in user TSconfig. However, method
      BackendUtility::getModTSconfig() violated this principle and
      had a special merge strategy that allowed ommitting the 'page.'
      prefix. This has been marked as deprecated in the TSconfig docs for
      various years and has been lately removed in the docs altogether,
      but the code still existed.
      The patch moves this merge into BackendUtility::getPagesTSconfig()
      and properly deprecates this case. Usages of getModTSconfig() are
      changed to use getPagesTSconfig() directly, dropping the artificial
      'properties' and 'value' sub arrays and omitting some rather expensive
      string operations at the same time.
      This obsoletes getModTSconfig() and a couple of related methods.
      Additionally, BackendUserAuthentication->getTSConfig() has been
      abused frequently to operate on different arrays than it's own userTS.
      Those usages are dropped with the patch. Handing over arguments to
      getTSConfig() is now deprecated, effectively reducing the method a getter.
      This reduces the API down to BackendUtility::getPagesTSconfig($pid)
      and BackendUserAuhtentiction->getTSConfig() both just returning the
      entire array. This simplified API can now be documented in the docs.
      Change-Id: I4bbb066c1d4e2edbc0182f7967897a1558cc3c0d
      Resolves: #85016
      Related: #84982
      Releases: master
      Tested-by: default avatarTYPO3com <>
      Reviewed-by: Jan Helke's avatarJan Helke <>
      Tested-by: Jan Helke's avatarJan Helke <>
      Reviewed-by: Anja Leichsenring's avatarAnja Leichsenring <>
      Tested-by: Anja Leichsenring's avatarAnja Leichsenring <>
      Reviewed-by: Christian Kuhn's avatarChristian Kuhn <>
      Tested-by: Christian Kuhn's avatarChristian Kuhn <>
  17. 15 Mar, 2018 1 commit
  18. 29 Jan, 2018 1 commit
    • Oliver Hader's avatar
      [BUGFIX] NewContentElementWizardController to NewContentElementController · 8bff8c83
      Oliver Hader authored and Oliver Hader's avatar Oliver Hader committed
      NewContentElementWizardController, which has been introduced for TYPO3 v9
      to render the new content element process in a dedicated modal was just a
      duplicate of the existing NewContentElementController class with some
      minor adjustments and code flow enhancements (names, empty checks).
      However, there have been several side effects like:
      * hook implementing NewContentElementWizardHookInterface would have been
        called by both object instances, having different public properties -
        the most common access to $parentObject->id or ~->sys_language would
        have failed to to property visibility and change names
      * the JavaScript closure callback to adjust the URL when interacting in
        the browser was hard-coded to modal rendering, with still having the
        possibility to render the old behavior e.g. in the web>list view
      To overcome these flaws both mentioned classes have been merged since the
      functionality was not that much different anyway. Besides that different
      JavaScript client scopes ('window' or 'list_frame') are forwarded to the
      according object instances.
      Resolves: #83705
      Releases: master
      Change-Id: I472a7ec8a5d06c05e6c7053bf98b5cfacb69f9d9
      Tested-by: default avatarTYPO3com <>
      Reviewed-by: Nicole Cordes's avatarNicole Cordes <>
      Tested-by: Nicole Cordes's avatarNicole Cordes <>
      Reviewed-by: Susanne Moog's avatarSusanne Moog <>
      Tested-by: Susanne Moog's avatarSusanne Moog <>
  19. 30 Nov, 2017 1 commit
  20. 08 Nov, 2017 1 commit
  21. 02 Oct, 2017 1 commit
  22. 23 Aug, 2017 1 commit
  23. 17 Aug, 2017 1 commit
  24. 12 May, 2017 1 commit
  25. 17 Feb, 2017 2 commits
  26. 06 Feb, 2017 1 commit
    • Benjamin Kott's avatar
      [!!!][FEATURE] Streamline Fluid Styled Content and CSS Styled Content · 80fec593
      Benjamin Kott authored and Benni Mack's avatar Benni Mack committed
      CSS Styled Content has been a long time the preferred way of rendering
      content in the frontend. Fluid Styled Content was introduced as
      successor of CSC, but the feature set diverged from the beginning. The
      lack of flexibility and incomplete feature set in comparision to CSC
      made it hard to migrate existing instances.
      Since TYPO3 CMS 7.6 Fluid-Templates are the defined standard and
      official recommendation for content rendering. The feature set of FSC is
      now matching CSC. Both content renderings are now streamlined to be
      fully compatible with each other. For the period of CMS 8 LTS CSC will
      share the same capabilities to make an transition as easy as possible.
      CSC is now deprecated and goes into maintenance mode and will be removed
      with CMS 9.
      For compatibility, CSC is now supporting Textmedia that was before
      exclusive to FSC. But also FSC has learned some tricks from CSC. Fluid
      Styled Content has now support for all content elements prior existing
      only in CSC, this includes "Text", "Text and Images" and "Images". Also
      for example "Frames", "Space before" and "Space after" are now again
      featured across both content rendering methods.
      Releases: master
      Resolves: #79622
      Resolves: #72422
      Resolves: #75466
      Resolves: #71570
      Resolves: #71484
      Change-Id: I7d2a9072baad508b6b87470b847444b91e7323fb
      Reviewed-by: Andreas Fernandez's avatarAndreas Fernandez <>
      Tested-by: Andreas Fernandez's avatarAndreas Fernandez <>
      Reviewed-by: Markus Klein's avatarMarkus Klein <>
      Tested-by: Markus Klein's avatarMarkus Klein <>
      Reviewed-by: Benni Mack's avatarBenni Mack <>
      Tested-by: Benni Mack's avatarBenni Mack <>
  27. 16 Jan, 2017 1 commit
  28. 04 Dec, 2016 1 commit
  29. 01 Dec, 2016 1 commit
  30. 27 Oct, 2016 1 commit
  31. 26 Oct, 2016 1 commit
  32. 09 Oct, 2016 1 commit
  33. 30 Aug, 2016 1 commit
  34. 03 Jun, 2016 1 commit
  35. 28 May, 2016 2 commits
  36. 05 May, 2016 1 commit