Closed geertsmichael closed 4 years ago
Drag & Drop rendering using the path instead of the SKU is actually currently working as designed. The Content/Asset Finder at the moment requires a Sling resource and returns that resource path.
I understand the different behavior is actually not optimal but currently something we can not change easily.
Ok, so CIF components should always work in both ways then (path and sku based)? What is the preferred way for linking to a product in your opinion? If that's SKU, then I propose a PostProcessor to remove the /var/commerce/... part.
Ok, so CIF components should always work in both ways then (path and sku based)? Yes, at least this applies for all CIF core components.
If that's SKU, then I propose a PostProcessor to remove the /var/commerce/... part. That is not possible ootb we can not simply remove it because a) we still need
/var/commerce/products
for the product bindings config and b) we can not remove any customer data!
Thank you.
Expected Behaviour
When dragging a Product on a page, from the "Product Content Finder" in Touch UI. It renders a path to "/var/commerce/products/magento-products/men/tops-men/MH02". When configuring the path from the dialog, just the product SKUs is used "MH02".
Steps to Reproduce
What is the correct way of defining products in a dialog? Are both ok and should all our components work with both a path & a sku?
Platform and Version
AEM 6.4.5 CIF Connector 0.7.1 CIF Core Component 0.6.0