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. 19 Dec, 2017 1 commit
  2. 13 Dec, 2017 1 commit
  3. 12 Dec, 2017 4 commits
  4. 11 Dec, 2017 1 commit
  5. 07 Dec, 2017 1 commit
  6. 30 Nov, 2017 1 commit
  7. 29 Nov, 2017 1 commit
  8. 27 Nov, 2017 1 commit
  9. 03 Nov, 2017 1 commit
  10. 16 Oct, 2017 1 commit
  11. 09 Sep, 2017 1 commit
  12. 08 Sep, 2017 1 commit
    • Benni Mack's avatar
      [!!!][BUGFIX] Separate sys_history from sys_log db entries · d047b314
      Benni Mack authored
      Before, the history module fetched info about "modified records" from
      sys_history+the authoritive user from a coupled sys_log entry.
      
      Info about "insert" and "delete" was fetched from sys_log solely.
      
      However, when using a scheduled cleanup task to truncate sys_log
      then all history information is useless (see bug report).
      
      The patch introduces a new RecordHistoryStore as an abstraction
      for adding history entries (currently done solely within DataHandler).
      
      It adds some additional, necessary SQL fields to sys_history to
      store all information in there and creates an update wizard
      to migrate all coupled sys_history/sys_log entries to a
      new sys_history entry itself.
      
      Additionally, the whole existing "RecordHistory" class is
      now only necessary for fetching the so-called ChangeLog,
      for a page or a specific record, and to do rollbacks, preparing
      the history records so they can be worked on.
      
      The whole logic for fetching the GET/POST parameters is moved
      into the "ElementHistoryController", everything that is only possible
      via Fluid is moved from the RecordHistory object and the
      ElementHistoryController into the view.
      
      Referencing from sys_log (Log module) into sys_history is
      now done the other way around, storing information about
      the corresponding history entry inside sys_log.
      As a side-effect, sys_log should load faster.
      
      Abstraction basis:
      - sys_history is the only source of truth about the history of a record
      - sys_log contains a reference to an history entry now
      (inside sys_log.log_data) to link from the backend log module
      - RecordHistoryStore exists for tracking changes to records
      - RecordHistory is for retrieving, compiling the history/changelog and rollbacks
      - ElementHistoryController is doing PSR-7 style request/response
      handling and preparing data for the view
      - Fluid is handling more view functionality now, removing
      the need for doing <f:format.raw> everywhere in the templates.
      
      Sidenotes:
      * Data within sys_history is now stored as JSON, not serialized anymore
      * Adding/deleting was previously stored in sys_log only, is now within sys_history
      * Moving records is now tracked (but not evaluated yet)
      * Highlight/Snapshot functionality within the Backend Module
      was removed
      
      This functionality is built so it can also be used within Extbase
      persistence and in FE in general in a future iteration.
      
      Resolves: #55298
      Resolves: #71950
      Releases: master
      Change-Id: I354317609099bac10c264b9932e331fa908c98be
      Reviewed-on: https://review.typo3.org/53195
      
      Reviewed-by: Andreas Fernandez's avatarAndreas Fernandez <typo3@scripting-base.de>
      Tested-by: Andreas Fernandez's avatarAndreas Fernandez <typo3@scripting-base.de>
      Tested-by: default avatarTYPO3com <no-reply@typo3.com>
      Reviewed-by: Joerg Kummer's avatarJoerg Kummer <typo3@enobe.de>
      Tested-by: Joerg Kummer's avatarJoerg Kummer <typo3@enobe.de>
      Reviewed-by: Benni Mack's avatarBenni Mack <benni@typo3.org>
      Tested-by: Benni Mack's avatarBenni Mack <benni@typo3.org>
      d047b314
  13. 23 Aug, 2017 1 commit
  14. 30 Jul, 2017 1 commit
  15. 28 Jul, 2017 1 commit
  16. 26 Jul, 2017 1 commit
  17. 06 Jul, 2017 1 commit
  18. 28 Jun, 2017 1 commit
  19. 09 Jun, 2017 1 commit
  20. 02 Jun, 2017 1 commit
  21. 18 Apr, 2017 1 commit
  22. 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-on: https://review.typo3.org/51686
      
      Reviewed-by: Nicole Cordes's avatarNicole Cordes <typo3@cordes.co>
      Tested-by: Nicole Cordes's avatarNicole Cordes <typo3@cordes.co>
      Reviewed-by: Benni Mack's avatarBenni Mack <benni@typo3.org>
      Tested-by: Benni Mack's avatarBenni Mack <benni@typo3.org>
      eb049dba
  23. 16 Feb, 2017 2 commits
  24. 14 Feb, 2017 1 commit
  25. 04 Feb, 2017 1 commit
  26. 03 Feb, 2017 1 commit
  27. 30 Jan, 2017 1 commit
  28. 11 Jan, 2017 1 commit
  29. 31 Dec, 2016 1 commit
  30. 22 Dec, 2016 1 commit
  31. 21 Dec, 2016 1 commit
  32. 01 Dec, 2016 1 commit
  33. 26 Oct, 2016 2 commits
  34. 19 Oct, 2016 1 commit
  35. 18 Oct, 2016 1 commit