1. 15 Dec, 2020 1 commit
  2. 20 Jul, 2020 1 commit
  3. 25 May, 2020 1 commit
  4. 27 Apr, 2020 1 commit
  5. 14 Apr, 2020 1 commit
  6. 30 Mar, 2020 1 commit
  7. 22 Feb, 2020 1 commit
  8. 10 Feb, 2020 1 commit
  9. 15 Jan, 2020 2 commits
  10. 29 Nov, 2019 1 commit
  11. 23 Apr, 2019 1 commit
  12. 03 Dec, 2018 1 commit
  13. 08 Dec, 2017 1 commit
    • Markus Hoelzle's avatar
      [!!!][FEATURE] Move extension configuration to install tool · ebf0f1a7
      Markus Hoelzle authored and Benni Mack's avatar Benni Mack committed
      With #82254 LocalConfiguration serialized array EXT/extConf has been
      changed to a not serialized array in EXTENSIONS. This patch follows
      up on this task an finishes various tasks:
      
      * An install tool silent upgrader upmerges given EXT/extConf settings
        to EXTENSIONS array. The resulting EXTENSIONS array does not contain
        dots for sub paths in its array key anymore and is accessible with a
        new ExtensionConfiguration->get() API to fetch values and whole
        extension config.
      * A new API is introduced to get() and set() extension specific
        configuration, is documented and used throughout the core to not
        unserialize old EXT/extConf anymore. Setting values updates legacy
        EXT/extConf to new values including compatible 'dot' ending on
        nested array configurations.
      * If extensions come with new configuration items in ext_conf_template.txt
        a silent upgrader of the install tool synchronizes these to the
        EXTENSIONS and old extConf array. Extension authors can rely on that
        and always fetch new keys from the new ExtensionConfiguration->get()
        API right away. The synchronization is also triggered when new
        extensions are loaded or extensions are updated via the extension
        manager.
      * Core usages are adapted to the new API.
      * Next to the main get() / set() API, the extension configuration
        form is extracted from the extension manager and put into the install
        tool as a new card in "Settings". The code below is streamlined
        and encapsulated with just a couple of public methods in class
        'ExtensionConfigurationService' as internal class for use in install
        tool and extension manager.
      
      Resolves: #82368
      Related: #82254
      Releases: master
      Change-Id: I88568fa355f8f6fd5acc9850dcdd718fdd9a1b2e
      Reviewed-on: https://review.typo3.org/54034
      
      
      Tested-by: default avatarTYPO3com <no-reply@typo3.com>
      Reviewed-by: default avatarDaniel Gorges <daniel.gorges@b13.de>
      Tested-by: default avatarDaniel Gorges <daniel.gorges@b13.de>
      Reviewed-by: Andreas Fernandez's avatarAndreas Fernandez <typo3@scripting-base.de>
      Reviewed-by: Benni Mack's avatarBenni Mack <benni@typo3.org>
      Tested-by: Benni Mack's avatarBenni Mack <benni@typo3.org>
      ebf0f1a7
  14. 22 Aug, 2017 1 commit
    • Christian Kuhn's avatar
      [!!!][TASK] Extension manager: Drop "Download SQL Dump" · 15819601
      Christian Kuhn authored and Benni Mack's avatar Benni Mack committed
      The em in "Installed Extensions" has a button "Download SQL Dump"
      for all extensions that provide ext_tables.sql. On click, an sql
      dump file is sent.
      
      This feature is severely flawed:
      * Dumps of extensions that add fields to existing tables contain
        a 'drop table' of these tables, the 'import into' statements are
        broken and only (try to) add these fields again. This easily
        leads to hazard in DB if importing such a dump.
      * There are no charset specs and other meta data whatsoever in the dump.
      * The dump is not dbal compatible, field definitions and imports
        are incomplete.
      
      We assume nobody really used this feature in a sane way, even at
      this prominent position in em. The lack of bug reports to this
      broken feature and the fact there have been zero changes in this
      area since main em refactoring years ago support this view.
      
      There are way better options to retrieve proper data specifications:
      * The list module has a csv export
      * Ext:impexp supports export and import in a much better way
        including proper relation handling and other options.
      * Low level db exports and backups should be done on cli or
        with more powerful guis like phpmyadmin or other db engine
        specific tools.
      
      The feature is dropped without substitution.
      
      The v8 backport of this patch will just remove the button from
      the em list view, but keep all code.
      
      Change-Id: Ia027e7498c5464af04c49675987a696ee3a06070
      Resolves: #82148
      Releases: master, 8.7
      Reviewed-on: https://review.typo3.org/53764
      
      
      Tested-by: default avatarTYPO3com <no-reply@typo3.com>
      Reviewed-by: Georg Ringer's avatarGeorg Ringer <georg.ringer@gmail.com>
      Tested-by: Georg Ringer's avatarGeorg Ringer <georg.ringer@gmail.com>
      Reviewed-by: Benni Mack's avatarBenni Mack <benni@typo3.org>
      Tested-by: Benni Mack's avatarBenni Mack <benni@typo3.org>
      15819601
  15. 13 Jul, 2017 1 commit
  16. 14 Jun, 2017 1 commit
  17. 20 Feb, 2017 1 commit
  18. 15 Feb, 2017 1 commit
  19. 12 May, 2016 2 commits
  20. 06 May, 2016 1 commit
  21. 30 Dec, 2015 1 commit
  22. 09 Nov, 2015 1 commit
  23. 30 Oct, 2015 1 commit
  24. 14 Oct, 2015 1 commit
  25. 02 Sep, 2015 1 commit
  26. 01 Sep, 2015 1 commit
  27. 25 Jul, 2015 1 commit
  28. 03 Jun, 2015 1 commit
  29. 13 Apr, 2015 1 commit
  30. 06 Mar, 2015 1 commit
  31. 04 Mar, 2015 1 commit
  32. 26 Feb, 2015 1 commit
  33. 07 Feb, 2015 1 commit
  34. 06 Feb, 2015 1 commit
  35. 05 Jan, 2015 1 commit
  36. 03 Jan, 2015 1 commit
  37. 30 Nov, 2014 1 commit
  38. 26 Nov, 2014 1 commit