Magento 2.3: Import fails if configurable attribute has an equal sign in its value

[viniciusfabri]

Preconditions (*)

1. Magento 2.3.2 (2.3-develop also works) - PHP 7.1.26
2. Sample data Installer

Steps to reproduce (*)

1. Change one of the attributes used by the configurable products (Size for instance) to have an = sign in its value
2. Export a configurable product that uses this attribute
3. Try to import the CSV from the previous step

Expected result (*)

1. Product should be imported correctly

Actual result (*)

1. Product import fails

Description

This happens because when Magento is creating the product variations, it uses the equal sign as a separator, but if the attribute value has an equal sign in it, it breaks. We fixed this by adding a limit of '2' to the explode calls in these lines:
https://github.com/magento/magento2/blob/2.3-develop/app/code/Magento/ConfigurableImportExport/Model/Import/Product/Type/Configurable.php#L576
https://github.com/magento/magento2/blob/2.3-develop/app/code/Magento/ConfigurableImportExport/Model/Import/Product/Type/Configurable.php#L637

[m2-assistant]

Hi @viniciusfabri. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.3-develop instance - upcoming 2.3.x release

For more details, please, review the Magento Contributor Assistant documentation.

@viniciusfabri do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[m2-assistant]

Hi @dhoang89. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[dhoang89]

@magento I'm working on it

[VladimirZaets]

Hi @viniciusfabri. Thank you for your report.
The issue has been fixed in #25194 by @dhoang89 in 2.4-develop branch
Related commit(s):

• cded4b1f2a72c9f6cf568d4c85ff31a16c0d61ac
• 904b2342c7f7ce391103091d1c9e0406af247aed
• c983d415d2592e93dcbc96abe1ad23ef45b2fda5
• c721ae4d574002a30cf8d98ff2c2ebfd59d7e91f
• e9226fe1d99c6e25378a5032d8f3b3007335ebc9
• 2dc4f1e9adc7f6f943680ce8eba1d2f243263dba
• 2dd6b141ae43a6b9ce924909cddf535a0225c949

The fix will be available with the upcoming 2.4.0 release.