1. 04 Nov, 2020 5 commits
  2. 03 Nov, 2020 3 commits
  3. 21 Oct, 2020 1 commit
  4. 15 Aug, 2020 1 commit
  5. 04 Aug, 2020 1 commit
    • Benni Mack's avatar
      [TASK] Reduce usage to tx_ter_extensions · 99038b21
      Benni Mack authored
      This patch changes
      - the extensions.xml generator
      - various logic regarding checks if a version exists
      to not query the tx_ter_extensions database table anymore.
      Now the only place where tx_ter_extensions is actually used
      is the SOAP API Upload and the Migration to tx_terfe2_* db structure
      which will be migrated in the next patch.
  6. 28 Jul, 2020 1 commit
    • 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.
  7. 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).
  8. 21 Jul, 2020 1 commit
    • Benni Mack's avatar
      [!!!][TASK] Drop usage of tx_ter_extensionkeys · e5ee1dcd
      Benni Mack authored
      The database table tx_ter_extensionkeys containing all registered
      extensionkeys is dropped in favor of "tx_terfe2_domain_model_extension".
      This table was synced already anyways, and can now be used within extensions.typo3.org
      without having to sync with a cronjob anymore.
      Breaking: The information about "title" and "description" is removed, as it wasn't
      required via the Web GUI when registering a key already.
      The sync task / TER importer now only imports the uploaded versions, the SOAP API
      now creates records directly in tx_terfe2_domain_model_extension when
      registering a new extension key.
      The One-Time-Migration-Script by tomalo (ImportAllExtensionKeysTask) is
      now removed as it is not needed anymore.
  9. 14 Jul, 2020 1 commit
  10. 13 Jul, 2020 1 commit
    • Benni Mack's avatar
      [FEATURE] Add ExtensionVersion API · 62fe2acc
      Benni Mack authored
      A new API class "ExtensionVersion" deals with a specific uploaded
      version of an extension.
      This class is responsible for checking sanitized versions, and serves
      as entrypoint to hide the logic behind "tx_ter_extensions" (and soon "tx_ter_extensiondetails"), by also handling deletion, updating reviewstate
      or uploading of new extension versions.
      On top, all TYPO3_DB calls are removed from EXT:ter with this change, moving
      more actual logic out of the SOAP API endpoints.
      In addition, the non-SOAP-API is now using non-static calls, as all
      logic is wrapped in a doUpload() method.
  11. 06 Nov, 2019 1 commit
  12. 04 Nov, 2019 2 commits
  13. 08 Aug, 2019 1 commit
  14. 28 May, 2019 1 commit
  15. 22 May, 2019 1 commit
  16. 20 May, 2019 1 commit
  17. 14 Mar, 2019 1 commit
  18. 23 Nov, 2018 1 commit
  19. 06 Nov, 2018 1 commit
  20. 12 Jul, 2018 1 commit
  21. 06 Jun, 2018 2 commits
    • Helmut Hummel's avatar
      Improve consistency and usability for composer name handling · 3bd919c8
      Helmut Hummel authored and Thomas Löffler's avatar Thomas Löffler committed
      Issue validation error when given composer name does not match
      the one in latest version.
      Remove composer name on import, when persisted composer name does not match
      the one in uploaded version.
      Simplify eID again, as we can now rely on composer_name in extension table
      being correct.
    • Helmut Hummel's avatar
      Make it possible to confirm a composer name for an extension · 40b50d14
      Helmut Hummel authored and Thomas Löffler's avatar Thomas Löffler committed
      A checkbox lets users confirm they uploaded the extension
      to Packagist and they own the package there.
      Additionally, when this box is checked the composer name
      needs to be provided as double confirmation.
      If this composer name is valid, registered on Packagist
      and matches the composer name of the latest uploaded
      extension version, the composer name is persisted.
  22. 31 Mar, 2018 1 commit
  23. 09 Mar, 2018 1 commit
  24. 14 Nov, 2017 1 commit
  25. 03 Nov, 2017 2 commits
  26. 23 Oct, 2017 1 commit
  27. 19 Oct, 2017 1 commit
  28. 15 Oct, 2017 3 commits
  29. 21 Sep, 2017 1 commit