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. 27 Jan, 2017 1 commit
  2. 26 Jan, 2017 1 commit
    • Christian Kuhn's avatar
      [!!!][FEATURE] FormEngine element level refactoring · 84be5e61
      Christian Kuhn authored
      The patch introduces a new API on FormEngine element level
      that substitutes the old "wizards" / renderWizard() API
      with a more powerful system.
      
      Single wizards are now split into one of three categories:
      * An informational wizard
      * A control button / icon
      * A true wizard with additonal functionality
      
      Method renderWizards() is still called in elements for compatibility
      reasons if people added own scrip/popup/userFunc wizards, but all
      core wizards are migrated.
      
      The patch significantly cleans the HTML of single elements, especially
      HTML stuff that was added by the SingleFieldContainer is now put down
      to single elements, while main HTML wraps formerly done by renderWizards()
      is fetched "up" to single elements. This gives single elements full
      control about the main HTML it is producing, which is a must have
      preparation in order to further advance in this area and to switch
      single elements to fluid rendering in one of the next steps.
      
      The patch brings a pretty huge list of TCA changes and
      simplifications, all TCA changes are supported by TCA migration,
      so existing extensions should benefit out of the box and just
      get deprecations logged.
      
      Change-Id: I45083e14e45bbf40c06267b51c9d0b7c15e2f7ab
      Resolves: #79440
      Resolves: #70032
      Releases: master
      Reviewed-on: https://review.typo3.org/51151
      
      Tested-by: default avatarTYPO3com <no-reply@typo3.com>
      Reviewed-by: Wouter Wolters's avatarWouter Wolters <typo3@wouterwolters.nl>
      Tested-by: Mona Muzaffar's avatarMona Muzaffar <mona.muzaffar@gmx.de>
      Reviewed-by: Benni Mack's avatarBenni Mack <benni@typo3.org>
      Tested-by: Benni Mack's avatarBenni Mack <benni@typo3.org>
      Reviewed-by: Christian Kuhn's avatarChristian Kuhn <lolli@schwarzbu.ch>
      Tested-by: Christian Kuhn's avatarChristian Kuhn <lolli@schwarzbu.ch>
      84be5e61
  3. 25 Jan, 2017 1 commit
  4. 23 Jan, 2017 1 commit
  5. 18 Jan, 2017 1 commit
  6. 17 Jan, 2017 1 commit
  7. 11 Jan, 2017 1 commit
  8. 04 Jan, 2017 1 commit
  9. 03 Jan, 2017 1 commit
    • Christian Kuhn's avatar
      [!!!][TASK] Improve flex and TCA handling in FormEngine · 38a1bc5d
      Christian Kuhn authored and Anja Leichsenring's avatar Anja Leichsenring committed
      The patch adapts a series of nasty form engine areas to more solid
      code. The evaluate condition code is rewritten and works much better
      in flex form scenarios. The suggest wizard and svg tree are much
      more solid in flex forms. The group element is rewritten
      towards a better readable and easier to refactor code, dropping
      method dbFileIcons(). A bunch of issues is resolved along the way.
      
      * TCA "default" now works in flex form section container elements
      * The "displayCond" parser is now strict and throws exceptions on
        invalid syntax and wrong referenced fields to help debugging
        faulty display conditions
      * TCA displayCond on flex fields can now be prefixed with the
        sheet name and can reference field values from neighbor sheets
      * TCA displayCond now works with flex section containers
      * TCA flex section container now throw an exception if select or
        group fields configure a MM relation - this is not supported
      * TCA ctrl requestUpdate field is dropped, onChange=reload is now allowed
        not only on flex form fields, but also on normal columns fields
      * TCA tree now works as section container element and initializes
        correctly on new records and new containers
      * GroupElement rewrite to drop dbFileIcons()
      * config option maxitems now optional for type=group and type=select
        and defaults to "many items allowed"
      * inline now works in "fancy" flex situations with "new" records
        by handing the final dataStructureIdentifier around
      * FormEngine no longer loads extJS
      
      Change-Id: Id1d081627529cc1502bb198389e5bd69372815cd
      Resolves: #78899
      Resolves: #72307
      Resolves: #75646
      Resolves: #76637
      Resolves: #72106
      Resolves: #78824
      Resolves: #76793
      Resolves: #68247
      Resolves: #69715
      Related: #78460
      Related: #67198
      Related: #72294
      Releases: master
      Reviewed-on: https://review.typo3.org/50879
      
      Tested-by: default avatarTYPO3com <no-reply@typo3.com>
      Reviewed-by: Benni Mack's avatarBenni Mack <benni@typo3.org>
      Tested-by: Benni Mack's avatarBenni Mack <benni@typo3.org>
      Reviewed-by: Anja Leichsenring's avatarAnja Leichsenring <aleichsenring@ab-softlab.de>
      Tested-by: Anja Leichsenring's avatarAnja Leichsenring <aleichsenring@ab-softlab.de>
      38a1bc5d
  10. 20 Dec, 2016 2 commits
  11. 13 Dec, 2016 1 commit
  12. 07 Dec, 2016 1 commit
  13. 03 Dec, 2016 2 commits
  14. 02 Dec, 2016 4 commits
  15. 01 Dec, 2016 2 commits
  16. 18 Nov, 2016 3 commits
  17. 17 Nov, 2016 1 commit
  18. 13 Nov, 2016 1 commit
  19. 12 Nov, 2016 1 commit
  20. 09 Nov, 2016 1 commit
  21. 08 Nov, 2016 1 commit
  22. 07 Nov, 2016 1 commit
    • Christian Kuhn's avatar
      [!!!][TASK] Flex form data structure refactoring · 9b7fd177
      Christian Kuhn authored and Susanne Moog's avatar Susanne Moog committed
      Method BackendUtility::getFlexFormDS() does two things at once:
      It finds a data structure by given data (TCA, row, ...) and then
      parses it.
      This construct gives tons of headaches, since the methods never
      exposes where a specific data structure came from and the lookup
      mechanism is complex. Especially if a flex form is used in
      combination with ajax requests later, the core has massive issues
      since the location can not be found out later again.
      
      To solve that, the patch splits getFlexFormDS() into two methods:
      First method "FlexFormTools->getDataStructureIdentifier()" gets
      TCA and row and locates a specific structure. It returns an
      "identifier" that points to that unique data structure. This
      identifier can be later hand around easily.
      The second method "FlexFormTools->parseDataStructureByIdentifier()"
      then gets this identifier again, fetches the data structure the
      identifier points to, and parses it.
      
      Change-Id: I38264e8a4a6f956c12e9e50f6039d3d09af0f03a
      Resolves: #78581
      Releases: master
      Reviewed-on: https://review.typo3.org/48212
      
      Tested-by: default avatarTYPO3com <no-reply@typo3.com>
      Tested-by: Claus Due's avatarClaus Due <claus@phpmind.net>
      Reviewed-by: Wouter Wolters's avatarWouter Wolters <typo3@wouterwolters.nl>
      Reviewed-by: Susanne Moog's avatarSusanne Moog <susanne.moog@typo3.org>
      Tested-by: Susanne Moog's avatarSusanne Moog <susanne.moog@typo3.org>
      9b7fd177
  23. 05 Nov, 2016 1 commit
  24. 31 Oct, 2016 1 commit
  25. 26 Oct, 2016 3 commits
  26. 24 Oct, 2016 1 commit
  27. 20 Oct, 2016 1 commit
  28. 09 Oct, 2016 1 commit
  29. 08 Oct, 2016 2 commits