Cant add & to attributes

[fbkaasa]

Preconditions (*)

1. Magento Commerce 2.2.6
2. Production and Staging environment

Steps to reproduce (*)

1. Add a brand to the manufacturer attribute (works)
2. Add a brand that contains & ( IE: Toni & Guy )

Expected result (*)

1. Expected that the brand would be saved and displayed as Toni & Guy

Actual result (*)

1. Prints an error ( or not actually an error, but something went wrong )
2. screenshot: https://mrkr.io/s/5c07a0889115ac1ac8a377e7/0

[magento-engcom-team]

Hi @fbkaasa. 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-engcom-team give me $VERSION instance

where $VERSION is version tags (starting from 2.2.0+) or develop branches (for example: 2.3-develop).
For more details, please, review the Magento Contributor Assistant documentation.

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

• yes
• no

[fbkaasa]

@magento-engcom-team give me 2.2.6 instance

[magento-engcom-team]

Hi @fbkaasa. Thank you for your request. I'm working on Magento 2.2.6 instance for you

[magento-engcom-team]

Hi @fbkaasa, here is your Magento instance.
Admin access: https://i-19571-2-2-6.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[magento-engcom-team]

Hi @engcom-backlog-nazar. 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-engcom-team 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!

• 5. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• 6. Add label Issue: Confirmed once verification is complete.

• 7. Make sure that automatic system confirms that report has been added to the backlog.

[fbkaasa]

I can verify that this issue persists on a clean Magento 2.2.6 install.

https://mrkr.io/s/5c07a2ae9115ac1ac8a377e9/0

Expected output was Toni & Guy

Hi @fbkaasa thank you for you report please look -> #19370

@fbkaasa this issue has already fixed in 2.3-develop branch, and will be available on 2.3.1 release.

[fbkaasa]

That is not acceptable. We cannot move clients to 2.3 as it was only released a week ago, and 3rd party modules does not fully support it.

Do you have a workaround for 2.2.6/2.2.7?

@fbkaasa #19375

[marcusirgens]

@engcom-backlog-nazar Which commit solves this issue? The current state of the file on the 2.2 branch is a huge rewrite from what we have in our code base at the moment: 815a767#diff-6268e71ecaea11cb09a0f07841941ac3
Will this be compatible with 2.2.6?

@fbkaasa @marcusirgens #18354
We will aim to release these changes as part of 2.2.8.