-
Notifications
You must be signed in to change notification settings - Fork 9.4k
Issue in product title with special chars in mini cart #13652
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@Sunil-Nethues , thank you for your report. |
Hello @magento-engcom-team , i have a fresh installation of v 2.2.2 The site can be seen at http://magento6.newsoftdemo.info/m22.2.2/fusion-backpack.html |
@Sunil-Nethues , thanks for you update. We cannot reproduce this issue with sample data too. |
@Sunil-Nethues I've also reproduced the issue but didn't find the issue with sample data on fresh composer install. |
@Ananth747 i have installed the magento2.2.2 using composer. then installed sample data using composer as well. After that i went to admin and changed the product name from Fusion Backpack to Fusion Backpack &trade and then tried to add it in cart. where i saw the issue. |
@Sunil-Nethues, thank you for your report. |
@Sunil-Nethues this is because Magento just shows the product name as a plain text, not a HTML. But, I ask myself it makes sense if allowing HTML in the product name? |
Hi @Sunil-Nethues. Thank you for your report. The fix will be available with the upcoming 2.3.0 release. |
The same issue I could get reproduced in cart summary section of checkout page. To fix that need to update Use: instead
|
Hi @Sunil-Nethues. Thank you for your report. The fix will be available with the upcoming 2.1.15 release. |
Hi @Sunil-Nethues. Thank you for your report. The fix will be available with the upcoming 2.2.5 release. |
…title with special chars. #14681
It looks to me like the fix only works for products with links? The knockout.js type on the non-link product title also needs changing to html. |
I'm running 2.2.7 and this problem has always occurred for us. It was never fixed in 2.2.5 |
Hi @InternetMedicineMan, |
For anyone having this issue in later versions, make sure that you don't have an extension that is re-introducing the problem. E.g. Aitoc PreOrders v2.2.0 re-introduced the issue via its own version of
|
Preconditions
Steps to reproduce
Expected result
Actual result
The text was updated successfully, but these errors were encountered: