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.
  5. 24 Jul, 2020 2 commits
  6. 23 Jul, 2020 2 commits
  7. 22 Jul, 2020 2 commits
  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. 16 Jul, 2020 2 commits
  10. 15 Jul, 2020 2 commits
  11. 14 Jul, 2020 8 commits
    • Benni Mack's avatar
      [!!!][TASK] Merge tx_ter_extensiondetails into tx_ter_extensions · 30ee6168
      Benni Mack authored
      There is a simple connection between tx_ter_extensiondetails and tx_ter_extensions
      (extensionuid field), but both tables always need to be kept in sync. This is unnecessary
      overhead. For this reason, all data is now moved into tx_ter_extensions (which will
      later be moved into tx_terfe2_domain_model_version).
      After adding the new fields to the database table "tx_ter_extensions",
      A onetime CLI command "ter:migrateextensiondetails" is executed
      and syncs all existing data into the main "tx_ter_extensions".
      "tx_ter_extensiondetails" can be dropped after the migration, as it is not
      used anymore at all.
    • Benni Mack's avatar
      [TASK] Drop unused ext_emconf v1 fields from TER v2 · 1050802d
      Benni Mack authored
      The following fields are not needed anymore and can be removed:
      * tx_terfe2_domain_model_version.load_order
      * tx_terfe2_domain_model_version.priority
      * tx_terfe2_domain_model_version.shy
      * tx_terfe2_domain_model_version.internal
      * tx_terfe2_domain_model_version.do_not_load_in_fe
      * tx_terfe2_domain_model_version.module
      * tx_terfe2_domain_model_version.modify_tables
      * tx_terfe2_domain_model_version.lock_type
      * tx_terfe2_domain_model_version.cgl_compliance
      * tx_terfe2_domain_model_version.cgl_compliance_note
      The fields are not used at all anymore.
    • Thomas Löffler's avatar
    • Benni Mack's avatar
      [TASK] Remove typo3db_legacy · 00730d21
      Benni Mack authored
      The package is not needed anymore and can be removed safely.
      In addition "ext-json" is added, in order to remove IDE issues.
    • Benni Mack's avatar
      [!!!][TASK] Drop evaluation of ext_emconf meta fields in TER v1 · f74c1b5e
      Benni Mack authored
      The database fields for TER1 are dropped, which are not needed
      since TYPO3 v6.0 anymore:
      * tx_ter_extensiondetails.datasize
      * tx_ter_extensiondetails.datasizecompressed
      * tx_ter_extensiondetails.codelines
      * tx_ter_extensiondetails.codebytes
      * tx_ter_extensiondetails.shy
      * tx_ter_extensiondetails.priority
      * tx_ter_extensiondetails.modules
      * tx_ter_extensiondetails.modifytables
      * tx_ter_extensiondetails.codingguidelinescompliance
      * tx_ter_extensiondetails.codingguidelinescompliancenote
      * tx_ter_extensiondetails.loadorder
      The SOAP API Endpoints still accept values matching this,
      however they are now unprocessed.
      All data is also still in tx_ter_fe2 version table, which will soon
      vanish as well.
    • Thomas Löffler's avatar
    • Thomas Löffler's avatar
      Remove empty file · 894507b0
      Thomas Löffler authored
    • Thomas Löffler's avatar
  12. 13 Jul, 2020 2 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.
    • 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.
  13. 08 Jul, 2020 2 commits
    • Benni Mack's avatar
      [TASK] Move constants to class constants · fb26f09e
      Benni Mack authored
      A new API class "ResultCodes" now covers all constants,
      and are replaced in order to keep the inline define() out
      of the tx_ter_helper class definition.
    • Benni Mack's avatar
      [FEATURE] Split out extensionqueue code · acfead60
      Benni Mack authored
      The DB table access "tx_ter_extensionqueue" is now centralized, its TCA
      is removed (as the "pid" information is not needed), and all access to this information
      is now moved to a new class called "UploadQueue", which can later be
      further separated.
      Fixes: #454
  14. 07 Jul, 2020 1 commit
    • Benni Mack's avatar
      [TASK] Centralize configuration for TER API · e2ae94f5
      Benni Mack authored
      A new Configuration class is added, which contains all information
      that was previously set in various places.
      This change
      * removes a dummy \stdObject containing random information
      * removes dependencies revolving around implicit dependencies in TSFE setup variables
      * Centralizes all options regarding repository path
      In addition, the tx_ter_api object does need any external dependencies
      loaded from e.g. pi-based plugins anymore. This way, the next step is
      to build a middleware for /ter and removing the plugin alltogether.
  15. 24 Jun, 2020 1 commit
    • Benni Mack's avatar
      [!!!][TASK] Refactor generation of extensions.xml.gz · 8f79744d
      Benni Mack authored
      This change re-implements the generation of the XML file for TYPO3 installations
      by moving the relevant code from EXT:ter to ter_fe2.
      CombinedExtensionRepository -> does the collection of available extensions
      ExtensionIndexService -> handles the XML generation and writing to files
      This way, all functionality can be separated and exchanged if necessary.
      A CLI command "ter:createExtensionIndexXml" is added which
      also shows some more useful output, however the logic is still in
      the "UpdateCurrentVersionListTask" class in EXT:ter.
      The methods:
      are removed, and thus, all of this logic is migrated to Doctrine DBAL.
      Root composer.json is adapted so the necessary PHP extensions are available
      in your IDE.
  16. 15 Jun, 2020 2 commits
  17. 14 May, 2020 1 commit
  18. 05 May, 2020 1 commit
  19. 04 May, 2020 1 commit
  20. 29 Apr, 2020 1 commit
  21. 28 Apr, 2020 2 commits
  22. 26 Apr, 2020 1 commit
  23. 21 Apr, 2020 1 commit