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. 06 Jan, 2021 1 commit
  2. 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 <>
  3. 14 Dec, 2020 1 commit
  4. 14 Nov, 2020 1 commit
  5. 05 Sep, 2020 1 commit
    • Christian Kuhn's avatar
      [!!!][TASK] Refactor create bookmark handling · 5be7b805
      Christian Kuhn authored and Anja Leichsenring's avatar Anja Leichsenring committed
      The backend shortcut / bookmark handlig API was designed to
      hand over relevant get/post arguments as key only (eg. 'id').
      The underlying code then pulled values from GET/POST or from
      SOBE->MOD_SETTINGS. This is ugly, there shouldn't be such
      magic: Only controllers know relevant keys and values, so
      it should hand them over directly to the shortcut API.
      The patch changes this:
      * Old and unused ViewHelper f:be.buttons.shortcut is deprecated.
      * ViewHelper be:moduleLayout.button.shortcutButton deprecates
        argument 'getVars' and adds new argument 'arguments'.
      * Class ShortcutButton has a new setter 'setArguments' that
        accepts all relevant argument key/value pairs to create a
        shortcut. Existing get/set related methods are deprecated.
      * Helper methods 'makeShortcutIcon' and 'makeShortcutUrl' of
        class ModuleTemplate are deprecated and implemented in class
        ShortcutButton directly.
      * All core usages are adapted to new API.
      * Shortcut handling was the last core usage of SOBE, so last
        $GLOBALS['SOBE'] = $this assignments can be finally removed.
      * Shortcuts to modules not directly reachable via main menu
        do not work due to limits of the module registration API. An
        example is the 'create multiple pages' controller. This issue
        exists before the patch, affected controllers no longer render
        a shortcut button for now.
      * The old code usually added the 'route' argument twice for shortcuts.
        This has been resolved. As a side effect, the comparison if a
        shortcuts exists (yellow shortcut icon) fails currently for existing
        shortcuts when the patch is applied: The comparison relies on
        direct string equality since shortcuts always store the final url in
        the database. This storage strategy should be changed with another
        patch that will solve the 'no yellow icon' issue at the same time.
      Change-Id: I3ccd2b8f6adab8e7780c5f9911fdea013ccfa99b
      Resolves: #92132
      Releases: master
      Tested-by: Andreas Fernandez's avatarAndreas Fernandez <>
      Tested-by: default avatarTYPO3com <>
      Tested-by: Anja Leichsenring's avatarAnja Leichsenring <>
      Reviewed-by: Andreas Fernandez's avatarAndreas Fernandez <>
      Reviewed-by: Anja Leichsenring's avatarAnja Leichsenring <>
  6. 02 Sep, 2020 1 commit
  7. 17 Aug, 2020 1 commit
  8. 15 Aug, 2020 2 commits
  9. 14 Aug, 2020 1 commit
    • Christian Kuhn's avatar
      [BUGFIX] Drop "All workspaces" tab from workspace module · 9c4aecd2
      Christian Kuhn authored and Andreas Fernandez's avatar Andreas Fernandez committed
      When "All workspaces" has been integrated somewhere before v6,
      it was advertised as a view to see changes from all workspaces.
      This however never worked: When calling the workspace module,
      "All workspaces" is empty. If switching to a workspace and then
      selecting "All workspaces", the tab shows only the changes of
      the selected workspace - identical to the normal workspace tab.
      Tracing this back in time, this behavior exists at least since v7.
      There is not a single bug report in forge about this.
      Since this tab is broken for such a long time without any
      report, we assume the functionality is barely needed.
      A better solution would be to show the number of existing
      changes next to the workspace name in the tab list, so editors
      can quickly see which specific workspace needs attention, and
      then switch to the workspace in question. This should be done with
      another patch since non-admins currently see only one workspace tab
      at a time, which needs another preparation patch to fix.
      This patch drops the broken "All workspaces" tab for now, preparing
      further bugfixes to finally end up with a working solution.
      Resolves: #91999
      Releases: master, 10.4
      Change-Id: I33f3cdba117b68927eb10447b0541d8975ed0a63
      Tested-by: default avatarTYPO3com <>
      Tested-by: Benni Mack's avatarBenni Mack <>
      Tested-by: Andreas Fernandez's avatarAndreas Fernandez <>
      Reviewed-by: Benni Mack's avatarBenni Mack <>
      Reviewed-by: Andreas Fernandez's avatarAndreas Fernandez <>
  10. 12 Aug, 2020 1 commit
  11. 15 Apr, 2020 1 commit
  12. 14 Apr, 2020 1 commit
  13. 31 May, 2019 1 commit
  14. 16 Apr, 2019 1 commit
  15. 01 Oct, 2018 1 commit
  16. 06 Jul, 2018 1 commit
  17. 11 May, 2018 1 commit
  18. 10 May, 2018 1 commit
  19. 25 Apr, 2018 1 commit
  20. 05 Mar, 2018 1 commit
  21. 01 Mar, 2018 1 commit
  22. 30 Nov, 2017 1 commit
  23. 09 Sep, 2017 1 commit
  24. 12 May, 2017 1 commit
  25. 28 Mar, 2017 1 commit
    • Wouter Wolters's avatar
      [TASK] Streamline return tags in phpdocs · eb049dba
      Wouter Wolters authored and Benni Mack's avatar Benni Mack committed
      The TYPO3 Core currently has no guidline how to handle phpdoc
      comments regarding @return annoations related to "void" and "null".
      In practice, these annotations have no additional value if no additional
      documentation is given.
      With this change, the php-cs-fixer will remove any unnecessary linebreaks
      within the comments above the @return annotation, as well as remove completely
      empty phpdoc comments because the @return annotation is removed.
      Please be aware, that once PSR-5 is accepted, this coding standard
      within the TYPO3 Core will change again, where there are currently
      some further proposal details like inheritance information.
      Resolves: #80454
      Releases: master
      Change-Id: Ie969d720684c0a75919fe5addd1c36ef5b12eb04
      Reviewed-by: Nicole Cordes's avatarNicole Cordes <>
      Tested-by: Nicole Cordes's avatarNicole Cordes <>
      Reviewed-by: Benni Mack's avatarBenni Mack <>
      Tested-by: Benni Mack's avatarBenni Mack <>
  26. 27 Oct, 2016 1 commit
  27. 30 Aug, 2016 2 commits
  28. 22 Aug, 2016 1 commit
  29. 17 Apr, 2016 1 commit
  30. 05 Mar, 2016 1 commit
  31. 19 Jan, 2016 1 commit
  32. 09 Jan, 2016 1 commit
  33. 30 Nov, 2015 1 commit
  34. 29 Nov, 2015 1 commit
  35. 20 Nov, 2015 1 commit
  36. 08 Nov, 2015 1 commit
  37. 13 Oct, 2015 1 commit
  38. 10 Oct, 2015 1 commit