1. 07 Aug, 2020 4 commits
  2. 06 Aug, 2020 8 commits
  3. 04 Aug, 2020 3 commits
  4. 03 Aug, 2020 5 commits
  5. 01 Aug, 2020 8 commits
  6. 30 Jul, 2020 3 commits
  7. 28 Jul, 2020 3 commits
    • Benni Mack's avatar
      [!!!][TASK] Remove flexible providers functionality · 15d40553
      Benni Mack authored
      There is some heavy legacy code regarding "where to find details/ the extension files"
      exactly in TER FE2.
      * Mirror -> use a mirror from extension repository (none given in TER), 5 tx_terfe2_domain_model_version entries
      * SOAP -> fetch the t3x from the SOAP API (no tx_terfe2_domain_model_version entry)
      * File -> default for all other files
      The type for each extension version is stored in "tx_terfe2_domain_model_version.extension_provider" and is removed
      to reduce massive code and complexity, having only the "FileProvider" in place
      removing the ProviderManager, Interface etc.
      MirrorService, MirrorPovider, SoapProvider, SoapService can be removed
      reducing cross-concern functionality.
    • Thomas Löffler's avatar
      Merge branch 'feature/move-extension-upload-out-of-soap-api' into 'develop' · 2205adce
      Thomas Löffler authored
      [TASK] Move extension upload out of SOAP API
      See merge request t3o/ter!536
    • Thomas Löffler's avatar
      Update TYPO3 CMS to v9.5.20 · 8958a972
      Thomas Löffler authored
  8. 24 Jul, 2020 5 commits
  9. 23 Jul, 2020 1 commit
    • Benni Mack's avatar
      [TASK] Move extension upload out of SOAP API · 84c3d7de
      Benni Mack authored
      The actual logic for uploading a new TER extension version
      is moved into the ExtensionVersion->upload() method,
      which handles all checks.
      This way, the tx_ter_api is not needed anymore outside
      the SOAP API (except for TerService, which will be adapted
      separately to work without tx_ter_api).