magento / magento/catalog-storefront

Export multi-store support

Open
#355 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PHP
Stars
7
Forks
16
PR merge metrics
No merged PRs in 30d

Description

### Preconditions (*)
Some of the data providers do not support multi-store and export data for one store.
Examples:
Magento\CatalogDataExporter\Model\Provider\Product\ProductOptions\DownloadableLinks
Magento\CatalogDataExporter\Model\Provider\Product\CustomizableOptions\ProductShopperInputOptions

### Steps to reproduce (*)
1. Setup two or more stores
2. In case of DownloadableLinks, create a downloadable product, set up links
3. Change link title on different store view scopes
4. Links are exported only for one store view

### Expected result (*)
1. Data providers support multi-store and export data for each store accordingly
2. Existing data providers are validated for multi-store support
3. Cover multi-store support with a test:
* Product in two stores with a different name, description, options with different labels
* Downloadable product with different link titles
* Bundle product with different labels for items

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by inspecting the Magento\CatalogDataExporter provider paths named in the issue, especially ProductOptions\DownloadableLinks and CustomizableOptions\ProductShopperInputOptions. Reproduce the behavior with two store views, then review the existing provider tests. Done means providers export store-specific names, descriptions, option labels, and downloadable link titles, with coverage for the listed product cases.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.