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. 09 Sep, 2017 5 commits
  2. 08 Sep, 2017 7 commits
  3. 07 Sep, 2017 1 commit
    • Benni Mack's avatar
      [TASK] Install Tool: Remove authentication from backend context · e3a0b0eb
      Benni Mack authored and Andreas Fernandez's avatar Andreas Fernandez committed
      Currently calling the install tool modules from within the Backend does a
      simple redirect with adding GET variables.
      That's the reason why you need to re-authenticate again, and the context
      is handed over as a query parameter, which is simply not needed at all.
      Now, the redirect is removed, as the Backend entrypoint / request handler
      handles the authentication of the backend user, and the standalone entry
      point deals with the install tool password etc.
      The context parameter is now detected by the entry point (!) as well,
      allowing to get rid of quite some code.
      There are some more consequences:
      - Calling the install tool from the backend does not validate if you configuration
      is set up (= recovery necessary) -> since you're already in the backend we guess
      you're fine anyway.
      - Redirect functionality is almost not needed anymore in the regular request handler
      - routeParameters concept was removed again (which was introduced a couple of weeks ago)
      Additionally, the contextService could be replaced at a later stage with just
      a string.
      Resolves: #82306
      Releases: master
      Change-Id: If7e4ddfaccf46cf93448d06c0ba9af81d5b9494c
      Reviewed-by: Romain Canon's avatarRomain Canon <>
      Tested-by: Romain Canon's avatarRomain Canon <>
      Tested-by: default avatarTYPO3com <>
      Reviewed-by: Andreas Fernandez's avatarAndreas Fernandez <>
      Tested-by: Andreas Fernandez's avatarAndreas Fernandez <>
  4. 05 Sep, 2017 2 commits
  5. 31 Aug, 2017 3 commits
  6. 29 Aug, 2017 1 commit
  7. 23 Aug, 2017 2 commits
  8. 22 Aug, 2017 2 commits
  9. 20 Aug, 2017 1 commit
  10. 18 Aug, 2017 2 commits
  11. 17 Aug, 2017 2 commits
  12. 15 Aug, 2017 1 commit
  13. 14 Aug, 2017 1 commit
  14. 11 Aug, 2017 3 commits
  15. 09 Aug, 2017 2 commits
  16. 01 Aug, 2017 1 commit
    • Christian Kuhn's avatar
      [FEATURE] Install tool: Extension scanner · 081ce36b
      Christian Kuhn authored
      The patch adds a new feature - the "extension scanner" - to the
      install tool. It is meant as a helper script for extension
      and project developers to quickly spot places in extension code
      that may need adaptions if upgrading to younger core versions.
      The scanner could later work with different languages, for now
      only scanning PHP files is supported. This is based on the great
      library nikic/php-parser which creates an AST from php source files
      and allows simple traversing.
      A series of matchers hooks into the traverser and scans for
      configured core deprecation or removals. Some additional matchers
      could be added if a core example evolves (for instance usage of
      dropped core constants).
      From now on, whenever the core deprecates or breaks existing core
      PHP API, an entry in one of the matcher configurations in
      ext:install/Configuration/ExtensionScanner/Php should be done.
      Since these API changes are documented via ReST files already, the
      configuration links to according ReST files. A bamboo integrity
      test script verifies those can be found.
      Furthermore, all Breaking-* and Deprecation-* ReST files since
      core version 9.x / master now need an additional Tag "FullyScanned",
      "PartiallyScanned" or "NotScanned". This is also checked by an
      integration test script in bamboo.
      The matcher configuration files are pretty straight forward and
      should be obvious if looking at
      This patch contains:
      * Add nikic/php-parser as dependency
      * New install tool gui to scan extensions in typo3conf/ext
      * Scanner infrastructure for PHP
      * Preparation and configuration for all current "master" / v9
        ReST files
      * Mark ReST files which are tagged with "FullyScanned" as "not affected"
        in install tool "Upgrade analysis" if no match was found
      * Integration script testing referenced ReST files are found
      * Integration script verifying Breaking- and Deprecation- ReST file
        contain "FullyScanned", "PartiallyScanned" or "NotSCanned" keyword.
      More information on this feature can be found at
      Change-Id: I760e88f9d929fdd710655fa0d25cb26291a7ed2b
      Resolves: #82014
      Releases: master
      Tested-by: default avatarTYPO3com <>
      Reviewed-by: Jan Helke's avatarJan Helke <>
      Tested-by: Jan Helke's avatarJan Helke <>
      Reviewed-by: Wouter Wolters's avatarWouter Wolters <>
      Reviewed-by: Frank Nägler's avatarFrank Naegler <>
      Tested-by: Frank Nägler's avatarFrank Naegler <>
      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. 31 Jul, 2017 3 commits
  18. 30 Jul, 2017 1 commit