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. 25 Apr, 2018 1 commit
  2. 17 Mar, 2018 4 commits
  3. 16 Mar, 2018 3 commits
  4. 01 Mar, 2018 1 commit
  5. 16 Feb, 2018 1 commit
  6. 29 Jan, 2018 1 commit
    • Oliver Hader's avatar
      [BUGFIX] NewContentElementWizardController to NewContentElementController · 8bff8c83
      Oliver Hader authored and Oliver Hader's avatar Oliver Hader committed
      NewContentElementWizardController, which has been introduced for TYPO3 v9
      to render the new content element process in a dedicated modal was just a
      duplicate of the existing NewContentElementController class with some
      minor adjustments and code flow enhancements (names, empty checks).
      
      However, there have been several side effects like:
      * hook implementing NewContentElementWizardHookInterface would have been
        called by both object instances, having different public properties -
        the most common access to $parentObject->id or ~->sys_language would
        have failed to to property visibility and change names
      * the JavaScript closure callback to adjust the URL when interacting in
        the browser was hard-coded to modal rendering, with still having the
        possibility to render the old behavior e.g. in the web>list view
      
      To overcome these flaws both mentioned classes have been merged since the
      functionality was not that much different anyway. Besides that different
      JavaScript client scopes ('window' or 'list_frame') are forwarded to the
      according object instances.
      
      Resolves: #83705
      Releases: master
      Change-Id: I472a7ec8a5d06c05e6c7053bf98b5cfacb69f9d9
      Reviewed-on: https://review.typo3.org/55479
      
      
      Tested-by: default avatarTYPO3com <no-reply@typo3.com>
      Reviewed-by: Nicole Cordes's avatarNicole Cordes <typo3@cordes.co>
      Tested-by: Nicole Cordes's avatarNicole Cordes <typo3@cordes.co>
      Reviewed-by: Susanne Moog's avatarSusanne Moog <susanne.moog@typo3.org>
      Tested-by: Susanne Moog's avatarSusanne Moog <susanne.moog@typo3.org>
      8bff8c83
  7. 13 Jan, 2018 2 commits
  8. 09 Jan, 2018 1 commit
  9. 27 Dec, 2017 1 commit
  10. 19 Dec, 2017 1 commit
  11. 09 Dec, 2017 1 commit
  12. 08 Dec, 2017 1 commit
  13. 30 Nov, 2017 1 commit
  14. 29 Nov, 2017 1 commit
  15. 27 Nov, 2017 1 commit
  16. 08 Nov, 2017 1 commit
  17. 06 Oct, 2017 1 commit
  18. 23 Aug, 2017 1 commit
  19. 09 Aug, 2017 1 commit
  20. 06 Jul, 2017 1 commit
  21. 12 May, 2017 1 commit
  22. 20 Apr, 2017 1 commit
  23. 31 Mar, 2017 1 commit
  24. 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
  25. 06 Feb, 2017 1 commit
    • Benjamin Kott's avatar
      [!!!][FEATURE] Streamline Fluid Styled Content and CSS Styled Content · 80fec593
      Benjamin Kott authored and Benni Mack's avatar Benni Mack committed
      CSS Styled Content has been a long time the preferred way of rendering
      content in the frontend. Fluid Styled Content was introduced as
      successor of CSC, but the feature set diverged from the beginning. The
      lack of flexibility and incomplete feature set in comparision to CSC
      made it hard to migrate existing instances.
      
      Since TYPO3 CMS 7.6 Fluid-Templates are the defined standard and
      official recommendation for content rendering. The feature set of FSC is
      now matching CSC. Both content renderings are now streamlined to be
      fully compatible with each other. For the period of CMS 8 LTS CSC will
      share the same capabilities to make an transition as easy as possible.
      CSC is now deprecated and goes into maintenance mode and will be removed
      with CMS 9.
      
      For compatibility, CSC is now supporting Textmedia that was before
      exclusive to FSC. But also FSC has learned some tricks from CSC. Fluid
      Styled Content has now support for all content elements prior existing
      only in CSC, this includes "Text", "Text and Images" and "Images". Also
      for example "Frames", "Space before" and "Space after" are now again
      featured across both content rendering methods.
      
      Releases: master
      Resolves: #79622
      Resolves: #72422
      Resolves: #75466
      Resolves: #71570
      Resolves: #71484
      Change-Id: I7d2a9072baad508b6b87470b847444b91e7323fb
      Reviewed-on: https://review.typo3.org/51065
      
      
      Reviewed-by: Andreas Fernandez's avatarAndreas Fernandez <typo3@scripting-base.de>
      Tested-by: Andreas Fernandez's avatarAndreas Fernandez <typo3@scripting-base.de>
      Reviewed-by: Markus Klein's avatarMarkus Klein <markus.klein@typo3.org>
      Tested-by: Markus Klein's avatarMarkus Klein <markus.klein@typo3.org>
      Reviewed-by: Benni Mack's avatarBenni Mack <benni@typo3.org>
      Tested-by: Benni Mack's avatarBenni Mack <benni@typo3.org>
      80fec593
  26. 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
  27. 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
  28. 02 Dec, 2016 1 commit
  29. 01 Dec, 2016 1 commit
  30. 08 Nov, 2016 1 commit
  31. 05 Nov, 2016 1 commit
  32. 26 Oct, 2016 1 commit
  33. 07 Oct, 2016 1 commit
  34. 30 Aug, 2016 1 commit