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. 09 Nov, 2019 2 commits
  2. 30 Oct, 2019 1 commit
  3. 09 Oct, 2019 1 commit
  4. 07 Oct, 2019 1 commit
  5. 11 Sep, 2019 1 commit
  6. 05 Sep, 2019 1 commit
  7. 29 Aug, 2019 1 commit
  8. 12 Jul, 2019 1 commit
  9. 05 Jul, 2019 1 commit
  10. 27 Jun, 2019 1 commit
  11. 31 May, 2019 1 commit
  12. 24 May, 2019 1 commit
    • Andreas Fernandez's avatar
      [!!!][TASK] Refactor client-side IRRE · 0842cea9
      Andreas Fernandez authored and Frank Nägler's avatar Frank Nägler committed
      This patch refactors the IRRE handling on client side, the JavaScript
      land has been rewritten to have a better structure and do less repeating
      on-the-fly calculations. Each IRRE container is represented by a
      independent instance of InlineControlContainer.
      
      Most of the internally used `scriptCall` directives have been removed.
      Currently, `scriptCall` can't get removed completely, as further
      refactorings in different areas are required.
      
      All of the "external" communication via `inline.foobar()` has been
      replaced by a event-driven approach. This also affects ElementBrowser
      windows, those use a minimalistic API based on postMessage.
      
      Some code that was never evaluated in ElementBrowser is considered dead
      and has been removed regarding inserting multiple items.
      
      A new sorting library has been added in order to replace jqueryui piece
      by piece.
      
      Executed command:
      
          yarn add --dev sortablejs
      
      On PHP side, some code has been removed as well since the rewritten client
      code is event-based and doesn't depend on external calls anymore.
      
      Resolves: #88182
      Releases: master
      Change-Id: I4176483d2882cef49fbaddb5e2e1914c1f76c908
      Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/59324
      
      Tested-by: default avatarTYPO3com <noreply@typo3.com>
      Tested-by: Georg Ringer's avatarGeorg Ringer <georg.ringer@gmail.com>
      Tested-by: Frank Nägler's avatarFrank Naegler <frank.naegler@typo3.org>
      Reviewed-by: Georg Ringer's avatarGeorg Ringer <georg.ringer@gmail.com>
      Reviewed-by: Frank Nägler's avatarFrank Naegler <frank.naegler@typo3.org>
      0842cea9
  13. 16 Mar, 2019 1 commit
  14. 15 Mar, 2019 1 commit
  15. 07 Mar, 2019 1 commit
  16. 28 Jan, 2019 1 commit
  17. 11 Oct, 2018 1 commit
  18. 30 Sep, 2018 1 commit
  19. 03 Sep, 2018 2 commits
  20. 02 Sep, 2018 1 commit
  21. 05 Aug, 2018 1 commit
  22. 18 Jul, 2018 1 commit
    • Christian Kuhn's avatar
      [FEATURE] Allow TCA description property · d421f7dc
      Christian Kuhn authored and Andreas Wolf's avatar Andreas Wolf committed
      When the site configuration module has been introduced, it came
      with a custom functionality to show an additional help text
      when editing site records between the field label and the field input.
      
      This useful feature is now changed into a general TCA feature
      available everywhere: A new field information node expansion / "wizard"
      is added to all form elements, the inline and flex containers: If
      the property "description" is set for a TCA column type (same array
      level as "label", it will show the value as localized string between
      the field label and the input section.
      
      There are three available render types for "wizard a-like" output:
      * Field information - text between label+field
      * Field control - buttons next to input sections like the link popup button
      * Field wizards - clickable stuff below the input section, for example
        the localization state selector
      If a field has been set to readOnly=true in TCA, field control and field
      wizards do not make sense to render since they are meant to act with the
      field value.
      The field information node however has only informational character
      which is useful for readOnly fields, too. Thus, this node expansion
      type is now the only one that is always rendered, even if a field has
      been set to readOnly.
      
      Note this patch is fully covered by ext:styleguide (master) to have
      examples for all changed elements now using the description property.
      
      Resolves: #85410
      Releases: master
      Change-Id: Idcfacafa19b8208614b653b8fac22ce47bca3b8f
      Reviewed-on: https://review.typo3.org/57397
      
      Tested-by: default avatarTYPO3com <no-reply@typo3.com>
      Reviewed-by: default avatarJörg Bösche <typo3@joergboesche.de>
      Tested-by: default avatarJörg Bösche <typo3@joergboesche.de>
      Reviewed-by: Andreas Wolf's avatarAndreas Wolf <andreas.wolf@typo3.org>
      Tested-by: Andreas Wolf's avatarAndreas Wolf <andreas.wolf@typo3.org>
      d421f7dc
  23. 28 Jun, 2018 1 commit
  24. 19 Jun, 2018 1 commit
  25. 25 Apr, 2018 1 commit
  26. 02 Mar, 2018 1 commit
  27. 20 Feb, 2018 1 commit
  28. 12 Feb, 2018 1 commit
  29. 13 Jan, 2018 1 commit
  30. 04 Jan, 2018 1 commit
  31. 27 Dec, 2017 2 commits
  32. 19 Dec, 2017 1 commit
  33. 30 Nov, 2017 1 commit
  34. 28 Nov, 2017 2 commits
  35. 27 Nov, 2017 2 commits