Skip to content
Snippets Groups Projects
  1. Apr 27, 2022
    • Oliver Bartsch's avatar
      [BUGFIX] Add maxwidth / maxheight parameters to YouTube oembed url · 310c615d
      Oliver Bartsch authored
      When uploading new assets to the filelist,
      the metadata (e.g. width and height) are
      automatically extracted from the corresponding
      files. This does not work for online media files,
      e.g. a YouTube video. Therefore, the corresponding
      services' oembed API is used to retrieve the
      related metadata.
      
      YouTube however changed their oembed API recently
      to always set a width of "200" and a height of "113"
      by default. This is obviously far too small for any
      use case.
      
      Since YouTube is following the oembed specification
      (https://oembed.com/#section2.2), it's possible to
      provide the "maxwidth" and "maxheight" parameters
      to the oembed URL. This way YouTube returns
      meaningful values for width and height.
      
      Actually a similar change was already done to
      the Vimeo integration in #85176. Vimeo however
      supports the custom "width" parameter, which is
      not mentioned in the specification and also not
      supported by YouTube.
      
      Resolves: #97481
      Related: #85176
      Releases: main, 11.5, 10.4
      Change-Id: If902cf17b12fc510592a48828d8304fad42e2bfa
      Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/74454
      
      
      Tested-by: default avatarcore-ci <typo3@b13.com>
      Tested-by: default avatarOliver Bartsch <bo@cedev.de>
      Reviewed-by: default avatarOliver Bartsch <bo@cedev.de>
      310c615d
  2. Apr 25, 2022
  3. Apr 20, 2022
  4. Apr 16, 2022
  5. Apr 12, 2022
  6. Apr 06, 2022
  7. Apr 05, 2022
  8. Mar 31, 2022
    • Christian Kuhn's avatar
      [TASK] runTests.sh: Remove .csv integrity handling · 2a47cb96
      Christian Kuhn authored
      When core functional tests started to heavily rely
      on CSV based import- and assertion files, we found
      that editing such .csv files in Microsoft Excel leads
      to warnings if the number of columns is not identical
      for each row.
      
      Script checkIntegrityCsvFixtures.php has then been
      established to verify all rows of .csv fixture files
      have the same amount of fields per file, and has been
      enabled as CI job to ensure all existing fixture
      files follow this.
      
      Nowadays, this restriction feels archaic: Devs actively
      working with these CSV files typically edit them in
      an IDE like PhpStorm directly and don't use Excel for
      this anymore. The PhpStorm plugin "Rainbox CSV" also
      helps by coloring these files and other alternatives
      like libreoffice do not have this 'all rows must have
      same number of colums' restriction.
      
      The patch drops the script, the runTests.sh usage and
      the CI calls. This has the additional advantage that
      line breaks for single fields are now possible, which
      will further improve handling and readability of field
      values in upcoming patches.
      
      Resolves: #97274
      Related: #83943
      Releases: main, 11.5, 10.4
      Change-Id: I2b4c2afc98c8471bccae1afb15e055182b563ee7
      Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/74131
      
      
      Tested-by: default avatarcore-ci <typo3@b13.com>
      Tested-by: default avatarChristian Kuhn <lolli@schwarzbu.ch>
      Reviewed-by: default avatarChristian Kuhn <lolli@schwarzbu.ch>
      2a47cb96
  9. Mar 29, 2022
  10. Mar 26, 2022
  11. Mar 25, 2022
  12. Mar 22, 2022
  13. Mar 15, 2022
  14. Mar 08, 2022
  15. Mar 07, 2022
  16. Feb 26, 2022
  17. Feb 22, 2022
  18. Feb 21, 2022
  19. Feb 20, 2022
  20. Feb 12, 2022
  21. Feb 08, 2022
  22. Jan 22, 2022
  23. Jan 20, 2022
  24. Jan 17, 2022
  25. Jan 13, 2022
  26. Jan 11, 2022
  27. Jan 10, 2022