1. 03 Aug, 2020 1 commit
  2. 01 Aug, 2020 1 commit
  3. 30 Jul, 2020 2 commits
  4. 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.
      15d40553
  5. 24 Jul, 2020 2 commits
  6. 23 Jul, 2020 3 commits
  7. 22 Jul, 2020 2 commits
  8. 21 Jul, 2020 3 commits
    • 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.
      e5ee1dcd
    • Benni Mack's avatar
      [BUGFIX] Use dirname instead of basename to create new upload · 1b0dd52e
      Benni Mack authored
      When uploading via SOAP API a wrong folder structure was created
      as basename() instead of dirname() was used.
      1b0dd52e
    • Benni Mack's avatar
      [BUGFIX] Use current user if no owner was specified · a60d6dd0
      Benni Mack authored and Thomas Löffler's avatar Thomas Löffler committed
      Fixes: #459
      a60d6dd0
  9. 16 Jul, 2020 2 commits
  10. 15 Jul, 2020 2 commits
  11. 14 Jul, 2020 12 commits
  12. 13 Jul, 2020 3 commits
    • Benni Mack's avatar
      [!!!][TASK] Drop localization and workspace fields for EXT:ter_fe2 · 3d426f0e
      Benni Mack authored
      All database tables in EXT:ter_fe2 are not versionable and non-translateable.
      
      For this reason, the fields are removed.
      3d426f0e
    • Benni Mack's avatar
      [BUGFIX] CGL cleanups · 8d3b85d1
      Benni Mack authored
      8d3b85d1
    • 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.
      62fe2acc
  13. 10 Jul, 2020 1 commit
  14. 09 Jul, 2020 3 commits
    • Benni Mack's avatar
      [FEATURE] Encapsulate "tx_ter_extensionkeys" access · 450ec6ae
      Benni Mack authored
      A new object "ExtensionKey" now allows to work with Extension Keys
      in the SOAP API with an object-oriented approach.
      
      This heavily reduces the tx_ter_helper class and removes helper
      functionality from tx_ter_api.
      
      The new ApiUser is now used to validate requests that need a valid
      user (registering an API key, or transferring ownership) as argument.
      450ec6ae
    • Benni Mack's avatar
      [BUGFIX] Clean up API code · b5f8bc19
      Benni Mack authored
      Some changes in the previous releases (especially loadBackendUser())
      now break results, where a virtual "_ter_" user is loaded.
      
      In addition, some previously unneeded public methods are
      now changed to protected.
      b5f8bc19
    • Benni Mack's avatar
      [TASK] Migrate authentication logic into ApiUser class · 0b8aac4c
      Benni Mack authored
      This change adds an object called "ApiUser" which can be built with
      a factory method "createFromSoapAccountData".
      
      Using the ApiUser allows for easy access of the user data, and
      covers both TSFE and LDAP dependencies which can later be exchanged
      easily for other purposes via a possible ApiUserInterface.
      
      The helper class usages are now reduced to continue removing
      legacy code and TYPO3_DB calls.
      0b8aac4c
  15. 08 Jul, 2020 2 commits