Changelog
| Documentation version | Pimcore bundle version | Shopware plugin version |
|---|---|---|
| 2026.10 | 12.7.0; 11.2.4 | 3.0.0 |
| 2026.3 | 12.4.0; 11.2.2 | 2.5.0 |
| 2025.11 | 12.2.2; 11.2.1 | 2.3.0 |
| 2025.9 | 12.0.0 | 2.3.0 |
| 2025.5 | 11.1.2 | 2.2.0 |
Pimcore 12.x
12.7.0
vorsicht
BC-Changes
AdapterAbstract::$listingis now nullable because virtual adapters have no listingArrayAdapterAbstracthas the new protected methodsgetRelationIds()andgetRelationIdsByFieldName()andTranslationServicethe new public methodgetSupportedLanguageMapping(); project subclasses that declare methods with these names but an incompatible signature cause a fatal error
- [feature] Add
ProductAdapterAbstractas base class for product export adapters; projects return the product entry frombuildProduct(Concrete $product, ?Concrete $mainProduct), variants come fromgetVariants(),isExportable()receives the main product of variants,id/uuidare added and the keys are checked againstgetAllowedProductKeys()/getAllowedTranslationKeys(), see Build a product export - [feature] Add the helpers
prepareTranslations()(supported Pimcore languages of the export target to Shopware locales oflanguage_mapping),applyTranslationFallback(),prepareVisibility(),preparePrice(),prepareRulePrice(),prepareManufacturer(),prepareDeliveryTime(),getNumericValue()andgetQuantityValueRangeSingleValue()toProductAdapterAbstractand the publicprepareObject()to build one product outside of an export - [feature] Add the command
twocream:shopware-connector:preview-productthat prints the product entry of an object, see Commands - [feature] Add the export target option
supported_languages- the Pimcore languages that the product adapters export, without it all enabled Pimcore languages - [feature] Add
CrossSellingTraitandCrossSellingProviderInterfaceto export cross-selling as the packagecross-selling(in delta exports only for the exported products including their variants, never for deleted products), includinggetCrossSellingChecksum()to detect cross-selling changes in delta exports; theArrayTransformercalls the publicresetCrossSelling()before everyconvert(), see Build a product export - [feature] Add
CategoryAssignmentAdapterAbstractas base class for category assignment export adapters - [feature] Add
GroupAdapterAbstractandVirtualAdapterInterfacefor virtual adapters that only serve as a selectable group in the export mask;ArrayAdapterAbstract::convert()returns no data for every virtual adapter - [improvement] Removed the "Total batch size" output from export mails
- [improvement] Removed the unreachable product batch export from the
ArrayTransformer(special handling of the adapter classesProductAdapterandProductListAdapter, which never existed in the bundle, andgetNextBatchData()) - [improvement] The deletion data of the
ObjectListenercomes from the first adapter of the class that overridesgetDeletedData()and returns non-null(the registration order only matters among overriding adapters), otherwise fromAdapterAbstract::getDeletedData(); the hard-coded special case for a product list class was removed - [improvement] Removed the unused batch handling (
main-job-id,final-batch, cached batch errors and logs) fromShopwareLogServiceandLogger - [bug] Import errors of exports with a
productadapter are now reported by mail instead of being silently dropped - [bug] Adapters are matched to objects regardless of the case of the class name in
twocream:shopware-connector:preview-product,AdapterCollector::getAdapterByConcrete()and theAssetCleanupTask; new helperAdapterCollector::isAdapterForObject()
12.6.4
- [improvement] Only objects whose class provides the Pimcore system date setter are loaded when processing Shopware acceptations
12.6.3
- [feature] Dependent adapters are now selected and locked automatically in the export mask
- [bug] Fixed lock interactions between dependent adapters and the export target switch in the export mask
12.6.2
- [improvement] The adapter configuration
source_folder_idsmay now also point to objects instead of folders
12.6.1
- [bug] Fixed an error when deleting the asset export journal entries of a deleted asset
12.6.0
- [feature] Added option
disabled_languagesto skip specific languages during export - [bug] Fixed an error that aborted the maintenance task
AssetCleanupTaskbefore the asset export journal was cleaned up
12.5.3
- [improvement] Made file and directory permissions of the SFTP transfer adapter configurable via the parameters
file_permissionsanddirectory_permissions
12.5.2
- [improvement] Added an option to the asset helper to set a custom asset name
- [bug] Fixed the file name in the
FieldSerializerwhen a custom asset name is used
12.5.1
- [improvement] Listings are now loaded in batches for improved performance
- [improvement] The application logger now displays basic information and provides a status overview
12.5.0
- [feature] Added transfer adapter
PimcoreAssetTransferAdapter(identifierpimcore_asset) to place export files in the Pimcore asset tree, the export job id is stored as asset metadataexportJobId - [feature] Added the optional export target configuration
asset_transferto use a separate transfer adapter for assets - [improvement] Added option
--userto the export command to associate the export job with a Pimcore user - [improvement] Added event
Twocream\ShopwareConnectorBundle\Events\ExportFilePlacedEvent::EXPORT_FILE_PLACED, dispatched after an export file was placed - [improvement] Added a type parameter to the
FieldSerializerto serialize original assets - [improvement] Added
league/flysystem-sftp-v3as suggested dependency - it is required to use the SFTP transfer adapter
12.4.2
- [bug] Fixed the default transfer adapter not being applied when the
transferconfiguration of an export target is omitted
12.4.1
- [bug] Fixed an error in the bundle installer
12.4.0
vorsicht
BC-Changes
- Refactored environment variables related to SFTP configuration into individual YAML parameters, see Configuration
- [feature] Moved SFTP transfer adapter configuration to YAML export target configuration, enabling individual configurations for different targets
12.3.6
- [bug] Fixed a bug causing delta exports to not work correctly
12.3.5
- [bug] Fixed asset serialization in FieldSerializer to get mime type, file name & file size from thumbnail instead of the original asset
12.3.4
- [bug] Fixed bug causing export permissions to not be identified
12.3.3
- [improvement] Fixed deprecation warning
12.3.2
- [improvement] Fixed several deprecation warnings
12.3.1
- [improvement] Minor performance improvements in SftpTransferAdapter
12.3.0
- [improvement] Improved normalization of asset URLs
- [improvement] Added retry strategy for SFTP connections
- [improvement] Optimized asset journal queries
12.2.2
- [bug] Fixed issue causing
.donefiles to not be processed properly
12.2.1
- [bug] Fixed minor issues affecting custom reports & the default directory resolver
12.2.0
- [feature] Added new adapter-based transfer system, enabling file operations on different storage systems
- [feature] Added possibility to configure a directory resolver to determine storage paths for files during export
- [feature] Added service for serialization of asset data types in export adapters
- [feature] Added custom reports for done, failed & queued export jobs
- [improvement] Asset domain is now optional in configuration
12.1.1
- [improvement] Improved examples in bundle configuration
12.1.0
- [feature] Added configuration for e-mail template branding
- [bug] Added missing bundle description
12.0.1
- [bug] Fixed faulty migration
12.0.0
- [improvement] Migrated this bundle to Pimcore 12
Pimcore 11.x
11.2.4
- [improvement] Only objects whose class provides the Pimcore system date setter are loaded when processing Shopware acceptations
11.2.3
- [bug] Fixed an error when deleting the asset export journal entries of a deleted asset
11.2.2
- [improvement] Fixed deprecation warnings
11.2.1
- [improvement] Optimized email logo embedding
11.2.0
- [feature] Added configuration for e-mail template branding
11.1.6
- [bug] Fixed deeplinks in log e-mails for non-numeric ids
11.1.5
- [improvement] Added method
getLanguageMapping()to theTranslationService
11.1.4
- [improvement] Added methods
getPimcoreLanguage()andgetShopwareExportLanguage()to theTranslationService
11.1.3
- [bug] Fixed an error in the thumbnail generator for objects without method
getClassName()
11.1.2
- [improvement] Minor improvements
11.1.1
- [bug] Removed strict dependency for
twocream/pimcore-rollbar-bundle
11.1.0
- [feature] Added scheduled executions
- [improvement] Optimized the log overview and detail-view
- [improvement] Optimized ex- and import log level behavior
- [bug] Removed strict dependency to
\Pimcore\AdvancedObjectSearchBundle
11.0.0
- [improvement] Migrated this bundle to Pimcore 11
Shopware
3.0.0
vorsicht
BC-Changes
- Replaced the
AbstractProductModule- the class is now abstract and does not handle the packageproductsanymore: the methodsgetHandledPackage,getEntityName,store,storeProductandgetProductDataand the property$variantPropertyGroupOptionPositionswere removed,validateonly resets the import caches (nofaultStatehandling anymore),fetchExistingProductis nowfinal,fetchTaxId(previouslyprivate) is nowfinal protected, takesfloat $taxinstead ofint $taxand returnsnullinstead of throwing an exception,fetchUnitId(previouslyprivate) is nowfinal protectedand takesstring $unit. Extend theProductModuleinstead, see Product import - Removed
Twocream\JsonImporter\Enum\ProductFaultState validateEntryof the product modules returns the names of the invalid fields like every other module (nofaultStatearrays anymore) - each problem skips the record with a warning, too long texts are truncated with a warning (seePayloadSanitizer)- Deleted products (
.meta.deleted) are deactivated instead of deleted, including the variants of a deleted main product and products that inheritactive(null) - The
ProductModulewrites products differently than the previousAbstractProductModule-stockdefaults to0(was999999) on create and is written on every update if delivered,minPurchaseandpurchaseUnithave no defaults anymore andreferenceUnitis written fromreference-unit(waspurchase-unit),mainVariantIdis only set fromvariant-listing-config.main-variant(variantListingConfigwithdisplayParent), variant options are only written from the keyoptionsof a variant (no longer derived fromproperties) and configurator settings are no longer deleted completely on every update - Relations of products (properties, variant options, configurator settings, variants) always mirror the import file - missing keys remove existing relations, variants that are no longer delivered are deactivated, also the children of a product without the key
variants. Delivered records are never deactivated as stale - records skipped by the validation (including their delivered variants), invalid variants and main records without a valid variant stay unchanged in Shopware (retainProducts), see Product import - Added parameter
array $keysToKeep = []to methodprepareRelationsin theAbstractModule- classes that override this method must add the parameter, see Register a new module - Added method
cleanupRelations(...): voidin theAbstractSyncModule- a method with the same name in a subclass must use the same signature including the return typevoid CategoryAssignmentModule: added hooksgetRootCategoryIdandgetCategoryExtensionIdColumn- subclasses with own methods of the same name must match the new signatures, anabstractredeclaration of these methods is a fatal error (Cannot make non abstract method ... abstract) - remove it and extend theCategoryAssignmentModuledirectly, overridegetCategoryExtensionIdColumn()with'id'if the id of the category extension equals the category id; unchanged assignments are no longer deleted and created again (fewer write events)- The default package order now follows the dependencies of the modules - subscribers of
PreHandlePackagesEvent::NAMEstill receive the sorted list and can change it, see Events - A sync batch that can not be written no longer aborts the import file - it is skipped and reported as error, the file ends with the resolution
success. Check the journal for errors instead of the resolution only, see Product import: FAQ - Deactivated products lose their own visibilities, products deactivated manually in the administration are reactivated by the next delivery if
activeis not delivered (main productstrue, variantsnull) - Records whose product number is used by another product (in Shopware or earlier in the file) are skipped with a warning - previously the whole product import failed. Free the product number in Shopware or correct it in the source system
- The default locale mapping of
JsonImportConfiguration::getLocaleMapping()mapsentoen_GB(default locale of Shopware) instead ofen_DE- projects with the Shopware localeen-DEthat receive the keyenmust restore the mapping viaLocaleMappingEvent::NAMEor an ownJsonImportConfiguration - Added protected and public methods to the module base classes - a method with the same name in a project module must use the same signature (an incompatible signature or a method with the same name as a
finalmethod is a fatal error):AbstractModule:getPackageDependencies,toInt,toFloat,toBool,parseDate,reportRecord,sanitizePayload,getPayloadSanitizer,resetReport,setReportLogger;AbstractSyncModule:syncBatchSafely,getSkippedRecordIds,resetCachesAfterFailedBatch,doImport(override);AbstractProductModule:doImportandcanBeDeleted(overrides),checkTranslations,resetImportCaches,resetCachesAfterFailedBatch,retainProducts,deactivateProducts,cleanupDeactivatedProducts,removeProductVisibilities,removeCrossSellingAssignments,removeCategoryAssignments,fetchReadableId,fetchReadableIds,deleteStaleProductProperties,deleteStaleProductVisibilities,deleteStaleProductOptions,deleteStaleConfiguratorSettings,extendCriteriaForExistingProductFetch,fetchTaxIdandfetchUnitId(previouslyprivate),fetchCurrencyId,fetchCmsPageType,collectProductIdsToDeactivate,resolveDeliveryTimeId,generateDeliveryTimeName,getOrCreateManufacturerIdByName,getOrCreateManufacturerId,getManufacturerMediaId,getProductCustomFields,getCustomFieldOptionValues,convertCustomFieldValue;JsonFileHandler:collectPackageDependencies;ModuleService:getLocales.finalareretainProducts,deactivateProducts,removeProductVisibilities,removeCrossSellingAssignments,removeCategoryAssignments,deleteStaleProductProperties,deleteStaleProductVisibilities,deleteStaleProductOptions,deleteStaleConfiguratorSettings,fetchTaxId,fetchUnitId,fetchCurrencyId,fetchCmsPageType,collectProductIdsToDeactivate,getProductCustomFieldsandgetCustomFieldOptionValues - Added protected properties and constants to the module base classes - a property or constant with the same name in a project module must be compatible (same type, constants not narrowed):
AbstractModule::$reportLogger(?LoggerInterface),AbstractSyncModule::$skippedRecordIds(array),AbstractProductModule::$taxIds,$currencyIds,$unitIds,$staleVariantIds,$importedProductIdsand$retainedProductIds(array),AbstractProductModule::PRODUCT_EXTENSION_ENTITY_NAME,PRODUCT_EXTENSION_ASSOCIATION_NAME,TAX_RATE_TOLERANCEandDELIVERY_TIME_UNITS,JsonFileHandler::$packageDependencySorter(PackageDependencySorter) import()replaces the report chapter of the module on every call - aChapterfetched withgetReport()beforeimport()is no longer filled. ReadgetReport()only afterimport()and set the logger withsetReportLogger()- Requires
twocream/shopware-6-core-plugin^2.3- update the core plugin together with the JSON importer
- [feature] Rewrote the
AbstractProductModuleas abstract base class for product import modules - it provides helpers likefetchExistingProduct,extendCriteriaForExistingProductFetch,fetchTaxId,fetchCurrencyId,fetchUnitId,getOrCreateManufacturerIdByName,deleteStaleProductProperties,deleteStaleProductVisibilities,deleteStaleProductOptions,deleteStaleConfiguratorSettings,deactivateProducts,getProductCustomFields,getCustomFieldOptionValues,convertCustomFieldValueandfetchReadableId(readable id in the report of deactivated products: Pimcore id of the product extension, otherwise the product number or the uuid;fetchReadableIdsreads them for a deactivation block with one query per table, an override offetchReadableIdis used per id) - [feature] Added
ProductModule- a generic import pipeline for the packageproducts(variants, properties, visibilities, rule prices, translations and product extension). The module is not registered by the plugin, register it or a subclass in your project. Rule prices: the rule ofgetRuleIdByMarketmust exist in Shopware (checked once per import), prices without a value in the default currency are skipped with a warning and the existing rule price is removed (unresolvable reference), a delivered rule price with an invalid value (net not numeric or negative) is reported and the existing rule price of the market is kept ($keptRulePriceIds), the gross price is calculated with the decimal tax rate. Delete-only relation entities (e.g.product_price,product_visibility,product_property,product_option,product_configurator_setting) are synced before the products, see Product import - [feature] Added hooks in the
ProductModuleto adapt the import to the project:getSalesChannelIdByMarket,getRuleIdByMarket,reportUnresolvedMarket,getAdditionalProductData,getProductExtensionData,getProductExtensionFieldMap,getProductExtensionTranslationKeyMap,cleanupAdditionalRelations,getProductFieldMap,getProductTranslationKeyMap,writeUnlocalizedCustomFieldsToAllLanguages,getManagedCustomFieldSetsandgetBatchSize- the pipeline stepsprepareVariants,prepareVariantListingConfig,prepareVariantOptions,prepareVisibilities,preparePrices,cleanupExistingProduct,prepareCustomFields,preparePurchasePrices,prepareCanonicalProduct,prepareCmsPage,prepareFeatureSet,prepareProductDataandwriteCanonicalProducts(with the helpersfindValidVariantIdandprepareConfiguratorGroupConfig) can be overridden as well - [feature] Added variant options - the key
options([{id, uuid}]of property options) of a variant is written as options of the variant, the configurator settings of the main product are built from the options of its delivered variants, all other options and configurator settings are removed - [feature] Added
AbstractTextSyncModuleas base class for simple text entities ({id, uuid, key, texts}) - overridegetSourceIdFieldif the Pimcore id is not stored in the fieldpimcoreId - [feature] Added method
getPackageDependenciesin theAbstractModuleand the servicePackageDependencySorter- packages are now sorted by the dependencies of their modules beforePreHandlePackagesEvent::NAMEis dispatched - [feature] Added method
cleanupRelationsin theAbstractSyncModuleto delete relations by their id that are no longer part of the import - [feature] Added parameter
$keysToKeepto methodprepareRelationsin theAbstractModule- the given keys of a relation are copied in camelCase to the prepared relation - [feature] Added hooks
getRootCategoryIdandgetCategoryExtensionIdColumnin theCategoryAssignmentModuleto limit the assignments to a category tree and to configure the id column oftwocream_category_extension - [feature] Added abstract product extension entities for
twocream_product_extension-AbstractProductExtensionDefinition,AbstractProductExtension,AbstractProductExtensionEntity,AbstractProductExtensionTranslationDefinitionandAbstractProductExtensionTranslationEntity. The associationproductExtensionis loaded automatically in the product import once the definition and the extension are registered, see Product extension - [feature] The default
getProductExtensionDataof theProductModulebuilds the product extension from the hooksgetProductExtensionFieldMapandgetProductExtensionTranslationKeyMap(default[]): only mapped keys delivered inproduct-extensionare written, the translations ofproduct-extension.translationsare mapped withprepareTranslation. Without maps, withoutproduct-extensionor without any delivered mapped key the extension is not written (null). Nested structures still need an override ofgetProductExtensionData, see Product import - [feature] Moving of variants between parents / to top-level - a product always gets the parent of its record (an existing variant delivered as top-level record is detached, a variant delivered under another main product is moved), moved products are not deactivated as stale variant of their old parent, each move is reported as info and the old parent is indexed again (child count, variant listing). A detached variant keeps its
stockifstockis not delivered (new context keysdetachedandexistingStockofprepareProductData), see Product import - [feature] Added batch-wise partial import -
syncBatchSafely(array $readableIds, array $additionalReadableIds = [], ?bool &$failed = null, bool $rememberSkipped = true)in theAbstractSyncModuleskips a sync batch that Shopware can not write (validation or database error, the batch is rolled back completely), reports one error with the readable ids of the batch and the cause (record and field if Shopware provides a pointer, manufacturer, unit and delivery time rows are described by the referencing record and their name) and continues with the next batch. Used by theProductModule(getBatchSize()main products including their variants), theCrossSellingModule(20 products) and theCategoryAssignmentModule(one category). There is no retry per record and the import does not remember skipped records - they are written again when they are delivered again (with delta exports re-export the records listed in the error), connection losses, deadlocks (after the retries of Shopware) and a transaction that is still open abort the import as before, see Product import: FAQ - [feature] Added
getSkippedRecordIds()and the hookresetCachesAfterFailedBatch()in theAbstractSyncModule- records of skipped batches are not deactivated as stale and no move messages are reported for them, caches of entities that are created before the products (manufacturers, units, delivery times) are reset after a failed batch - [feature] Added the detection of failures after the commit - if a listener of the write events throws after Shopware committed the batch, the error
Batch was written, but post-processing failedis reported and the records count as written (deactivation and moves are handled normally) - [feature] Added
Twocream\JsonImporter\Core\System\Import\Validation\PayloadSanitizer- checks a write payload against the DAL definition: too long strings are truncated, invalid integers, numbers, booleans and dates (type, range, database limits) are removed so Shopware keeps the current value, an empty date string is written asnull, nested entries (translations, rule prices, visibilities, delivery time) with an invalid required value are dropped, each change is returned as issue. Integers outsidePayloadSanitizer::INT_MIN/INT_MAXandwidth,height,lengthandweightof products outside[0, 10000000)(PayloadSanitizer::DEFAULT_FLOAT_RANGES) are removed, other ranges can be passed as third argument$floatRangesof the constructor (?DefinitionInstanceRegistry $registry = null, array $languageLabels = [], ?array $floatRanges = null) by overridinggetPayloadSanitizer. Static helperstoInt,toFloat,toBool,parseDate,isValidGtin,truncateanddescribeValue - [feature] Added
sanitizePayload,getPayloadSanitizer,toInt,toFloat,toBool,parseDateandreportRecordin theAbstractModule-sanitizePayloadreports each issue of thePayloadSanitizeras warning of the record - [feature] Added hook
sanitizeProductDatain theProductModule- every product and variant row (including the data ofgetAdditionalProductDataand the product extension) is sanitized right before it is queued,maxPurchaselower thanminPurchase(or 1) is not written, an EAN without valid GTIN check digit is only reported and imported anyway - [feature] Added the product number check
filterProductNumberConflictsin theProductModule(withnormalizeProductNumberandfetchProductIdsByProductNumbers, one query per batch) - a record whose product number is already used earlier in the import file under another uuid or by another product in Shopware (e.g. a deactivated product) is skipped with a warning, a main product including its variants, a variant only itself. Existing products affected by a conflict stay unchanged and are not deactivated (retainProducts). The comparison ignores surrounding spaces and the case. A record whose number still belongs to a Shopware product that is delivered in the same file with another number and is not written yet is deferred (including its variants) and checked again once after all batches - swapped numbers of two products stay a conflict and are reported with the hint to use a temporary number in the source system - [feature] Added typed custom fields to the
ProductModule-custom-fields{<technical name>: value}(not localized) andtranslations.<locale>.custom-fields{<technical name>: value}(localized, wins in its language) of products and variants. Names are resolved against the active custom fields of the sets related to products (loaded once per import), values are converted by the field type (int,float,bool,text,html,datetime,selectincl. multi select and configured options,entity/media uuids,number,priceas list of{currencyId, net, gross, linked}including the default currency,jsonand other types unchanged). Unknown names and invalid values are reported as warning and not written, the record is imported anyway. Values ofcustom-fieldsare written to all languages of the shop (hookwriteUnlocalizedCustomFieldsToAllLanguages,false= system language only). Only delivered keys are written,nullremoves the own value (Shopware stores JSONnulland skips it when merging, a variant inherits the value of its main product), keys of the sets of the hookgetManagedCustomFieldSets(default[]) that are not delivered are removed per language (existing custom fields are read once per batch), keys of other sets and plugins are never touched.translationsreturned bygetAdditionalProductDataare merged per language and field (customFieldsper key) instead of replacing the translations of the import, see Product import - [feature] Added variant inheritance to the
ProductModule- variants only requireid,uuidandproduct-number. A missing, empty ornullname of a delivered language is written asnull, an explicitnulloftax(never resolved to 0 %) andpriceis written asnull,nullof simple fields,manufacturer,unit,delivery-time, translation keys and custom fields is written asnull- Shopware inherits the value of the main product. Gross rule prices of a variant use its deliveredtax, without the keytaxits current tax in Shopware, with"tax": null(or as new or inheriting variant) the tax of the main product, an undeterminable tax rate keeps the current rule prices with a warning (new parameters?string $parentId = nulland?ProductEntity $product = nullofpreparePrices, new helperfetchTaxRatein theAbstractProductModule). Main and simple products keep the required checks (tax,price, names) - [feature] Added the fields
manufacturer-number,max-purchase,reference-unitandrestock-timeand the translation keyspack-unitandpack-unit-pluralto theProductModule - [feature] Added the fields
purchase-price,canonical-product,cms-page,feature-setandvariant-listing-configto theProductModule-purchase-price{net, gross}is written aspurchasePricesin the default currency likeprice(numeric, not negative),canonical-product{id, uuid}must exist in Shopware or be written in this import and is written after all batches (writeCanonicalProducts, chunks ofgetBatchSize()viasyncBatchSafely, not the product itself, not a product that is deactivated in this import - new helpercollectProductIdsToDeactivatein theAbstractProductModule),cms-pageis the uuid of an existing layout of the typeproduct_detail,feature-setthe uuid of an existing feature set (layouts and feature sets are loaded once per import and never created, new helperfetchCmsPageTypein theAbstractProductModule).variant-listing-config{display-parent, main-variant{id, uuid}, configurator-group-config[{id?, uuid, representation, expression-for-listings}]}of a main product overrides single keys of the defaultvariantListingConfig(displayParent: true) - the main variant must be a valid variant of the record, a group config entry needs an existing property group (once per group, the first wins), the representationbox,select,imageorcolorand a booleanexpression-for-listings(defaultfalse), the key is not written for variants and simple products. A missing key keeps the value,purchase-price: null,{}or[],canonical-product: null,""or[],cms-page: null,""or[]andfeature-set: null,""or[]remove it (variants inherit),variant-listing-config: nullwrites the default, invalid or unresolvable values are reported as warning and not written, the record is imported anyway - [feature] Added the field
delivery-timeand the helperresolveDeliveryTimeId(string|array $deliveryTime, string $contextId = '', string $recordInfo = '')- the uuid of an existing delivery time or{min, max, unit, name?}(unithour,day,week,monthoryear). An existing delivery time with the same values is reused, otherwise it is created once with the idmd5("delivery-time-<min>-<max>-<unit>")(name per locale fromname, otherwisegenerateDeliveryTimeName, e.g.1-3 days). Delivery times are never changed, a missing key keeps the assignment,nullor""removes it, invalid values are reported and not written - [feature] Added the manufacturer structure
{name, link?, description?: {<locale>: text}}and the methodgetOrCreateManufacturerId- a manufacturer delivered as string goes throughgetOrCreateManufacturerIdByName(a project method with this name is used for it), manufacturers are create-only (name, link and description are written on create, existing manufacturers are never changed), the image is only set by the new hookgetManufacturerMediaId(array $manufacturer, bool $exists): ?string(defaultnull= image untouched, also for existing manufacturers if the returned media differs) - [feature] Added hook
cleanupDeactivatedProducts(array $productIds)and the final helpersremoveProductVisibilities,removeCrossSellingAssignmentsandremoveCategoryAssignmentsin theAbstractProductModule- the hook is empty by default, syncs queued in the hook are written together with the deactivation of the block.removeCrossSellingAssignmentsdeletes the own cross-sellings of the products, removes the products from other cross-sellings and deactivates other cross-sellings that no longer have assigned products, see Product import - [feature] Added
setReportLoggerandresetReportin theAbstractModuleandgetLocalesin theModuleService - [feature] Added
LocaleMappingEvent::NAME(Twocream\JsonImporter\Core\System\Import\Event\LocaleMappingEvent) - subscribers can change the locale mapping ofJsonImportConfiguration::getLocaleMapping()in code, the event is dispatched once perModuleServicewith the locales of the Shopware languages. TheModuleServicehas the new optional constructor argument$eventDispatcher, see Events - [improvement] The product import synchronises the state of the import file - relations always mirror the record (existing visibilities keep their id, a changed visibility value is written), missing keys of simple fields are not written and
stockis set to0only when a product is created - [improvement] An explicit
"stock": nullis handled like a missing key -0on create, not written on update - [improvement] Unresolvable references of a product (markets, currencies, property options, variant options) are reported as warning per reference and not linked
- [improvement] A product with variants in Shopware that is delivered as simple product is reported as warning - its variants are deactivated, the product stays a container until they are deleted
- [improvement] Variants that are invalid in the import but exist in Shopware keep their configurator settings at the main product (options are read from Shopware)
- [improvement] Added package dependencies to the modules of the plugin -
attribute-valuesrequiresattributes,cross-sellingrequiresproducts,category-assignmentsrequiresproductsandcross-selling, theProductModulerequiresattributesandattribute-values - [improvement] Added optional constructor argument
$packageDependencySorterto theJsonFileHandler- subclasses that call the parent constructor with the previous arguments keep working - [improvement] The
CategoryAssignmentModuleclears its caches after eachstorecall - [improvement] The
AbstractProductModuleresets existing ids and caches on every import (resetImportCachesinvalidate- a subclass that callsdoImportwithoutimport/validatehas to call it itself), manufacturers and units are written before the products that reference them - [improvement] The report chapter of a module is written to the
.donejournal also if the module throws an exception - the errorImport of package "<package>" was aborted: <message>is added, the file still ends with the resolutionerror - [improvement] Each import starts with a new report chapter per module - long-running workers no longer carry over messages of earlier files.
setReportLogger()is the preferred way to set the report logger, a logger set viagetReport()->setLogger()is kept (read viaChapter::getLogger()) - [improvement] Delivered records without the key
activeare written as active (true) for main and simple products and as inherited (null) for variants - deactivated products are reactivated when they are delivered again - [improvement] A new main or simple product without a name in the system language is skipped with a warning (variants inherit the name, see variant inheritance), a product number longer than the DAL limit (64) is skipped (not truncated), a product number that only consists of spaces counts as missing and texts are written without surrounding spaces
- [improvement] Taxes are compared as decimal number with the tolerance
TAX_RATE_TOLERANCE(0.001) - 0 % and 7.7 % are found, taxes are loaded once per import and never created, if several taxes have the same rate the first by position wins - [improvement] An invalid
stockis reported and handled like a missing key, a negative stock is allowed - [improvement] Deactivated products (deleted records, their variants and stale variants) lose their own visibilities - already inactive candidates are cleaned up as well without being reported again, each block of 100 products is written atomically, a failing block is reported as error and the other blocks are still processed
- [improvement] A record that is marked as deleted and also delivered in the same import file is not deactivated (warning)
- [improvement] Failures while indexing the old main products of moved variants or while deactivating products are reported as error, the import continues
- [improvement]
isIdExistuses a hash lookup instead ofin_array- faster for large catalogues - [improvement] Deprecated
checkFieldLengthsandcheckTranslationFieldLengthsof theAbstractModule(tag:v4.0.0) - usesanitizePayload, the limits are read from the DAL definition - [improvement] Main prices (
price.net,price.gross) andtaxare parsed like rule prices (toFloat) -"1,5"and"7,7"are accepted, the validation uses the parsed value - [bug] Fixed the detection of stale assignments in the
CategoryAssignmentModule- existing assignments that are still part of the import are no longer deleted and created again - [bug] Fixed an error when
$syncsof anAbstractSyncModuleis read aftersync- the property is now reset to an empty array instead of being unset - [bug] Fixed a
TypeErrorincheckDamImagefor a missing image or uuid -nullis returned without message - [bug] Fixed tax rates with decimals (7.7 % was searched as 7 %) and the tax rate 0 % (rejected as missing)
2.5.2
- [bug] Fixed missing translations of meta title and meta description in the product import of the
AbstractProductModule- the keysmeta-titleandmeta-descriptionare now mapped to the Shopware fields, other translation keys are no longer passed to Shopware
2.5.1
- [improvement] Minor improvements
2.5.0
- [feature] Added icon to attribute extension - use
propertyGroup.propertyGroupExtension.translated.iconandpropertyGroup.propertyGroupExtension.iconType
2.4.3
- [improvement] Added method
getSkipIndexersin theAbstractSyncModuleto suppress some index sub-processes - if needed - [improvement] Improved performance of the category-assignment import by skipping the search keyword and SEO URL indexers
2.4.2
- [improvement] Improved memory usage of category-assignment import
2.4.1
- [improvement] Added method
cleanupEntityWrittenContainerEventin theAbstractModule- this is very useful if you handle more complex import structures with a lot of associations and multiple sync calls - [improvement] Split cross-selling import into multiple batches to prevent high database load
- [improvement] Improved memory usage of category-assignment import
2.4.0
- [feature] Added event
Twocream\JsonImporter\Core\Framework\MessageQueue\Event\PreHandlePackagesEvent::NAMEto support custom package order - this could be necessary if you import relational data before other packages
2.3.2
- [improvement] Added property
$disableElasticsearchSubProcessto theCategoryAssignmentModuleto suppress the Elasticsearch sub-processes after the import - if needed
2.3.1
- [feature] Added
AbstractProductModuleas base class for product import modules - [improvement] The
AbstractProductModuleremoves properties of existing products that are no longer part of the import and rebuilds their configurator settings - [improvement] Delete operations of an
AbstractSyncModuleare now synced before upsert operations
2.3.0
- [improvement] Migrated this plugin to Shopware 6.7
2.2.1
- [improvement] Removed the HTTP cache warm up after an import, it is no longer needed
2.2.0
- [feature] Added
PropertyGroupExtensionto support custom attribute locations - [improvement] Added
InjectImportFileInterfaceandInjectImportFileTraitto inject the whole json import file to the import-module that implements this interface - [bug] Fixed typo in english plugin name
2.1.3
- [bug] Fixed an invalid command call when creating the Elasticsearch/OpenSearch alias after the category-assignment import
2.1.2
- [bug] Fixed an error in the constructor of the
CategoryAssignmentModuleintroduced in 2.1.1
2.1.1
- [bug] Fixed the Elasticsearch/OpenSearch indexing after the category-assignment import
2.1.0
- [improvement] Added
SkipCacheClearInterfaceto suppress a cache clear after importing data of import-modules that implements this interface
2.0.0
- [improvement] Added support for projects without elasticsearch or opensearch
- [improvement] Migrated this plugin to Shopware 6.6
- [bug] Added missed translations