This project is mirrored from https://git.typo3.org/typo3/typo3.git. 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. 18 Jul, 2015 1 commit
  2. 16 Jul, 2015 1 commit
  3. 15 Jul, 2015 2 commits
  4. 14 Jul, 2015 2 commits
  5. 13 Jul, 2015 1 commit
    • Benni Mack's avatar
      [FEATURE] Introduce Request/Response based on PSR-7 · ab3729bb
      Benni Mack authored and Christian Kuhn's avatar Christian Kuhn committed
      The PSR-7 standard is adapted into the TYPO3 Bootstrap with a
      backwards-compatible layer.
      
      The PSR-7 implementation brings several new classes:
       * Message (the base for Requests and Responses)
       * Request (for Requests made within PHP)
       * ServerRequest and a factory based on the current system environment
       * Response
       * Uri (a unified API for fetching several parts of an URI)
      
      At any TYPO3 request a new ServerRequest object is created inside the
      Bootstrap and handed over to the RequestHandler which can then use this
      object for checking certain GET and POST variables instead of using
      GeneralUtility.
      
      The proper call (usually a Controller) creates a Response object that
      is handed back to the RequestHandler + Bootstrap. The TYPO3 Bootstrap
      will output anything related in the shutdown() method.
      
      An example is shown with the LoginController and currently hard-wired
      as no proper routing/dispatching is there yet.
      
      Currently this is an internal API as the rest (Dispatch/Router and
      Controller API) will follow once the base is in.
      
      Please note that the PSR-7 standard works with Value Objects meaning
      that it is not possible to modify any object but instead new objects
      will be created for Message, ServerRequest and Response if modified.
      
      The next steps are:
      * Integrate proper Routing + Dispatching for Backend Routes to register
        new BE requests
      * Migrate all AJAX Calls to use the new API and request / response
        handling
      * Introduce a common Base Controller for all regular BE requests which
        is based on Request/Response and works as a replacement for sc_base
      * Then: proper documentation for the whole bootstrap /
        dispatch + routing / controller logic
      * Integrate symfony console app into the CLI Bootstrap as alternative
        for Request/Response
      * Refactor TSFE to use Response / Request objects properly
      * Refactor redirects logic to use Response objects
      
      Resolves: #67558
      Releases: master
      Change-Id: I5b528284ecca790f784c7780b008356158343ee8
      Reviewed-on: http://review.typo3.org/40355
      
      
      Reviewed-by: default avatarHelmut Hummel <helmut.hummel@typo3.org>
      Tested-by: default avatarHelmut Hummel <helmut.hummel@typo3.org>
      Reviewed-by: Wouter Wolters's avatarWouter Wolters <typo3@wouterwolters.nl>
      Tested-by: Wouter Wolters's avatarWouter Wolters <typo3@wouterwolters.nl>
      Reviewed-by: Markus Klein's avatarMarkus Klein <markus.klein@typo3.org>
      Tested-by: Markus Klein's avatarMarkus Klein <markus.klein@typo3.org>
      Reviewed-by: Christian Kuhn's avatarChristian Kuhn <lolli@schwarzbu.ch>
      Tested-by: Christian Kuhn's avatarChristian Kuhn <lolli@schwarzbu.ch>
      ab3729bb
  6. 30 Jun, 2015 1 commit
  7. 18 Jun, 2015 1 commit
  8. 16 Jun, 2015 1 commit
  9. 20 May, 2015 1 commit
  10. 24 Mar, 2015 1 commit
  11. 23 Mar, 2015 1 commit
    • Benni Mack's avatar
      [!!!][FEATURE] Introduce Backend Routing · a08ce723
      Benni Mack authored
      A new Routing API is introduced in order to streamline
      the entrypoints to the TYPO3 Backend.
      
      All previous patches by Wouter for the dispatched modules
      are the foundation for this change.
      
      Instead of using the term "module" for anything linkable
      in the backend, the term "routes" fits more. A "module"
      or an ajax call is a derivative of a route, which will
      build on this foundation.
      
      Routes can be registered via
      Configuration/Backend/Routes.php in any extension
      and are loaded solely on Backend requests.
      
      The Routing API is inspired by the Symfony Routing
      framework and mostly compatible for now
      but the TYPO3 implementation only takes around
      20% of the needed logic.
      
      There are three new classes:
      - Route (a single route with a path and some options)
      - Router (API to match paths and generate URLs)
      - UrlGenerator (Generates the URL)
      
      This patch changes the entrypoint for
      login/logout to typo3/index.php/myroute/?token=...
      making index.php the only entrypoint to the
      TYPO3 Backend in the future and using the PATH_INFO
      functionality of the browser to store the route.
      
      The main RequestHandler of all Backend modules
      detects where a PATH_INFO is given and
      then resolves to a controller/action logic and checks
      for a valid token.
      
      Once this patch is in, all non-module entrypoints
      are moved to the new format.
      
      See http://wiki.typo3.org/Blueprints/BackendRouting
      for implementation details.
      
      Resolves: #65493
      Releases: master
      Change-Id: I91b5812c833c558794f70fd4504f2da452b1c3ce
      Reviewed-on: http://review.typo3.org/37476
      
      
      Reviewed-by: Nicole Cordes's avatarNicole Cordes <typo3@cordes.co>
      Tested-by: Nicole Cordes's avatarNicole Cordes <typo3@cordes.co>
      Reviewed-by: default avatarHelmut Hummel <helmut.hummel@typo3.org>
      Tested-by: default avatarHelmut Hummel <helmut.hummel@typo3.org>
      a08ce723
  12. 03 Mar, 2015 1 commit
  13. 01 Mar, 2015 1 commit