Commands
Export
php bin/console twocream:shopware-connector:export <mail> <system> --<ADAPTER_PACKAGE_NAME>
Description
With the export command, you can execute the Pimcore export via command instead of through the admin interface. The export is added to the queue.
Arguments
| Name | Required | Description |
|---|---|---|
mail | Yes | The email address to which information about the export should be sent |
system | No | Target system of the export |
Options
| Name | Shortcut | Description |
|---|---|---|
--<ADAPTER_PACKAGE_NAME> | None | An option is created for each adapter with its package name (e.g., --products).This option executes the export for that adapter. Multiple can be added. |
--pretty | -p | Outputs the JSON files formatted |
--export-job-id <EXPORT-JOB-ID> | -i | The job ID stored in the TmpStore object, following the format pimcore_export_<UNIX timestamp> |
--skip-delta | -d | Generates a full export, including unchanged files |
--user <USER> | -u | Pimcore username or user ID to be associated with the export job (e.g., for the "User" column in the log overview). Only taken into account if no --export-job-id is given |
Queue
php bin/console twocream:shopware-connector:queue
Description
This command processes the export jobs in the queue and executes them.
Reload Permissions
php bin/console twocream:shopware-connector:reload-permissions
Description
This command reloads all permissions for adapters and export target systems.
Preview product
php bin/console twocream:shopware-connector:preview-product <object-id> --system=<SYSTEM>
Description
The command prints the entry that every product adapter (ProductAdapterAbstract) of the class of the object creates via buildProduct(), including the variants (see "Build a product export"). No checksums are stored and no export file is written. buildProduct() is executed as in the export, assets copied by buildProduct() (e.g., via assetHelper()) are copied to the asset directory of the export target. As in the export, localized fields return their fallback values and unpublished objects are hidden in relations.
Arguments
| Name | Required | Description |
|---|---|---|
object-id | Yes | ID of the Pimcore object |
Options
| Name | Shortcut | Description |
|---|---|---|
--system <SYSTEM> | -s | Required. Configured export target that is used to build the entry (e.g., for assetHelper()) |
Output
- For every product adapter of the class, a section with the package name and the entry as JSON. If the adapter does not export the object (e.g.,
isExportable()returnsfalse), a note is printed - Errors, e.g., an unknown key, are printed without stack trace and end the command with the exit code
1. The same applies if--systemis missing, the object is not found or no product adapter exports the class - Warnings are printed if entries of
supported_languagesare not enabled Pimcore languages (they are not exported), no language is exported at all (no supported language is enabled in Pimcore) or the object is not published (it is built anyway, the export skips it)