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 2 commits
  3. 19 Dec, 2020 1 commit
  4. 18 Dec, 2020 2 commits
  5. 17 Dec, 2020 1 commit
    • Oliver Bartsch's avatar
      [!!!][TASK] Rework shortcut PHP API functionality · e4833fda
      Oliver Bartsch authored and Christian Kuhn's avatar Christian Kuhn committed
      To be able to introduce URL rewrites for the backend,
      the internal handling and registration of the shortcut
      PHP API is reworked.
      The Shortcut PHP API previously has the full URL of
      the shortcut target stored in the database. This lead
      to many problems such as shortcuts got invalid as soon
      as their target module changed its route path. Furthermore,
      this required unnecessary functionality like replacing
      tokens on URL creation.
      Therefore, a shortcut record now stores only the route
      identifier of the module to link to and necessary arguments
      in two new database columns. A upgrade wizard is in place
      to migrate existing data.
      The rework also required to deprecate some methods in
      the ShortcutButton API and a parameter signature change
      of the JavaScript function `TYPO3.ShortcutMenu.createShortcut()`
      which performs the AJAX call to create new shortcuts.
      Side effect, this also deprecated the last remains of
      xMOD_alt_doc.php in the core.
      Resolves: #93093
      Releases: master
      Change-Id: I07666a299651e4953b4adf2987fcd3469094c288
      Tested-by: default avatarTYPO3com <>
      Tested-by: Daniel Goerz's avatarDaniel Goerz <>
      Tested-by: Christian Kuhn's avatarChristian Kuhn <>
      Reviewed-by: Daniel Goerz's avatarDaniel Goerz <>
      Reviewed-by: Christian Kuhn's avatarChristian Kuhn <>
  6. 15 Dec, 2020 2 commits
  7. 14 Dec, 2020 3 commits
  8. 12 Dec, 2020 2 commits
  9. 11 Dec, 2020 1 commit
  10. 10 Dec, 2020 6 commits
  11. 09 Dec, 2020 1 commit
  12. 08 Dec, 2020 4 commits
  13. 07 Dec, 2020 2 commits
  14. 05 Dec, 2020 1 commit
  15. 04 Dec, 2020 3 commits
  16. 03 Dec, 2020 1 commit
  17. 01 Dec, 2020 1 commit
  18. 30 Nov, 2020 1 commit
  19. 29 Nov, 2020 2 commits
    • Christian Kuhn's avatar
      [TASK] Add application type to request · 3291239e
      Christian Kuhn authored
      The cardinal issue with constant 'TYPO3_MODE' is that it's
      value is NOT constant: It is defined early during bootstrap and
      derived from information that is hand over from entry point
      index.php's. Depending on this, value is either 'FE' or 'BE'.
      Using that constant or the related constant 'TYPO3_REQUESTTYPE'
      makes it impossible to change scope from backend to frontend
      in one PHP call. This actively blocks executing sub requests,
      use cases are for instance executing a frontend request within
      a running backend call (eg. view module), or executing frontend
      requests from cli (eg. some indexer).
      Dropping 'TYPO3_MODE' and its friends is thus a requirement to
      finally allow such scenarios. We can't get rid of the distinction
      between 'frontend' and 'backend' altogether since some legit use
      cases like different paths or security settings depend on it.
      Looking at TYPO3 bootstrap, the only class that 'knows' if it's
      frontend or backend are the Application classes of ext:frontend
      and ext:backend. They are the PSR-15 entry points, they create a
      first PSR-7 request object if it has not been given, and then
      call the PSR-15 middleware stack dispatcher to create a PSR-7
      response, starting with this first request object.
      The solution to get rid of 'TYPO3_MODE' is to add the information
      'I am a frontend or backend request' as attribute to the request
      object in the Application classes. To simplify things, the helper
      class ApplicationType is introduced that answers isFrontend() and
      isBackend() for a given request object.
      Documentation changelog files with full details on the impact of
      this change will be added with an upcoming patch that deprecates
      the constants in master.
      This patch targets master and v10: 'TYPO3_MODE' is used in
      extensions quite often. Having the API in both v10 and v11 helps
      extension developers to deliver deprecation free extensions that
      are compatible with both v10 and v11 in one version. Codewise,
      neither the 'applicationType' attribute nor the helper class
      harm in v10.
      Resolves: #92951
      Related: #92947
      Releases: master, 10.4
      Change-Id: Ia4ea637b252b774cf72492402e6be52ee4695242
      Tested-by: default avatarTYPO3com <>
      Tested-by: Anja Leichsenring's avatarAnja Leichsenring <>
      Tested-by: Simon Gilli's avatarSimon Gilli <>
      Tested-by: Christian Kuhn's avatarChristian Kuhn <>
      Reviewed-by: Anja Leichsenring's avatarAnja Leichsenring <>
      Reviewed-by: Simon Gilli's avatarSimon Gilli <>
      Reviewed-by: Christian Kuhn's avatarChristian Kuhn <>
    • Christian Kuhn's avatar
      [TASK] Use constant 'TYPO3' in global script files · 36a2051f
      Christian Kuhn authored and Anja Leichsenring's avatar Anja Leichsenring committed
      Avoid usage of constant 'TYPO3_MODE' as security gate
      in script files that don't run in class or callable context.
      Use new constant 'TYPO3' instead.
      Resolves: #92949
      Related: #92947
      Related: #92948
      Releases: master
      Change-Id: I95618793ed29b4b71e9e97ea8da124924d6753fc
      Tested-by: default avatarTYPO3com <>
      Tested-by: Daniel Haupt's avatarDaniel Haupt <>
      Tested-by: Anja Leichsenring's avatarAnja Leichsenring <>
      Reviewed-by: Daniel Haupt's avatarDaniel Haupt <>
      Reviewed-by: Anja Leichsenring's avatarAnja Leichsenring <>
  20. 27 Nov, 2020 2 commits
  21. 26 Nov, 2020 1 commit