1. 06 Jun, 2022 1 commit
  2. 18 Apr, 2022 1 commit
  3. 05 Feb, 2022 1 commit
  4. 02 Feb, 2022 1 commit
  5. 17 Jan, 2022 1 commit
  6. 07 Dec, 2021 1 commit
  7. 26 Nov, 2021 1 commit
  8. 17 Nov, 2021 1 commit
  9. 12 Oct, 2021 1 commit
  10. 07 Oct, 2021 1 commit
  11. 13 Sep, 2021 1 commit
  12. 23 Aug, 2021 1 commit
  13. 12 Aug, 2021 1 commit
  14. 15 Jul, 2021 1 commit
  15. 12 Jul, 2021 1 commit
  16. 10 Dec, 2020 1 commit
  17. 28 Sep, 2020 1 commit
  18. 15 Apr, 2020 1 commit
  19. 14 Apr, 2020 1 commit
  20. 02 Apr, 2020 1 commit
  21. 23 Mar, 2020 1 commit
  22. 29 Feb, 2020 1 commit
  23. 30 Jan, 2020 1 commit
  24. 30 Dec, 2019 1 commit
  25. 20 Dec, 2019 1 commit
  26. 19 Dec, 2019 1 commit
  27. 27 Nov, 2019 1 commit
  28. 23 Aug, 2019 1 commit
  29. 03 Jul, 2019 1 commit
  30. 12 Jun, 2019 1 commit
  31. 01 Oct, 2018 1 commit
  32. 29 Sep, 2018 1 commit
  33. 22 Jun, 2018 1 commit
  34. 15 Jun, 2018 1 commit
  35. 29 Mar, 2018 1 commit
  36. 02 Mar, 2018 1 commit
  37. 18 Jan, 2018 1 commit
    • Christian Kuhn's avatar
      [TASK] impexp: Remove size handling · e044ef20
      Christian Kuhn authored
      ext:impexp has a "size" display and adds size information
      to export formats for records file sizes. This is entirely
      removed with the patch - both from interface and .xml/.t3d
      exports:
      
      * The size handling on db records always made little sense,
        the default maximum size of 1MB was "never" hit, there
        wasn't even an input box to raise that limit, ever.
        This information is now just removed from the export formats.
      * The size handling on files is rather irrelevant with FAL,
        since FAL file integrity is checked with sha1 already. The
        size display during export in the interface for FAL files
        never worked since FAL migration in core v6.0 - It always
        displayed 0. Nobody ever cared, there is not even a forge
        issue about that.
      * Removing the 'size' column in the export interface - which
        only carried rather irrelevant information on record "size"
        only - simplifies the interface a bit.
      * The record size information in exports depends on used
        dbms due to different internal database types. Removing that
        makes exports more dbms agnostic. This can be seen with
        all the functional test fixture file changes coming with
        the patch - removing that reduces a maintenance nightmare
        in this area and improves the chance to align exports
        in between the functional testes on different dbms again.
      
      Note that exporting .xml/.t3d in v9 and importing it
      in a v8 instance does not work anyway due to more
      significant DB field related changes in v9 already.
      The effects of this patch could be easily mitigated
      on v8, but we were unable to create anything in v9 that
      is able to be imported in v8 again - and ext:impexp
      is not created to be an upgrade / download helper
      in the first place. Thus, ignoring size checks in
      v8 to mitigate effects of the file format change
      does not seem to be necessary and is not done.
      
      Change-Id: I0cae7b371b6ac027e27c9192ffa273dabc9795c7
      Resolves: #83606
      Releases: master
      Reviewed-on: https://review.typo3.org/55391
      
      
      Reviewed-by: Anja Leichsenring's avatarAnja Leichsenring <aleichsenring@ab-softlab.de>
      Tested-by: Anja Leichsenring's avatarAnja Leichsenring <aleichsenring@ab-softlab.de>
      Tested-by: default avatarTYPO3com <no-reply@typo3.com>
      Reviewed-by: default avatarReiner Teubner <rteubner@me.com>
      Tested-by: default avatarReiner Teubner <rteubner@me.com>
      Reviewed-by: Christian Kuhn's avatarChristian Kuhn <lolli@schwarzbu.ch>
      Tested-by: Christian Kuhn's avatarChristian Kuhn <lolli@schwarzbu.ch>
      e044ef20
  38. 27 Dec, 2017 1 commit
  39. 19 Dec, 2017 1 commit
  40. 27 Nov, 2017 1 commit