Magento2: Empty attribute label is displayed on product page when other language used.

[nowszy]

Preconditions

1. Clean instance of Magento 2.1.8
2. Store displayed in some foreign languege i.e. pl_PL
3. Simple product with some attribute visible on product page.

Steps to reproduce

1. Go to product page.
2. See attribute label ('none' translated to your foreign language) in the attributes section/

Expected result

1. 'none' label translated to other languages i.e. polish lang - 'brak' should not be displayed
2. comparisson in line 37 of app/code/Magento/Catalog/view/frontend/templates/product/view/attribute.phtml is changed to if ($_attributeLabel != __('none')) in order to not display 'none' translated to foreign language

Actual result

1. In the template app/code/Magento/Catalog/view/frontend/templates/product/view/attribute.phtml line 37 you have followin comparisson: if ($_attributeLabel != 'none') but at this part of code $_attributeLabel is already translated.

[korostii]

FYI: This has been reported may times before: #9295, #9161, #9531,

[orlangur]

Ok, so, there are (at least) two attempts to fix this issue. Both merged to develop and none to 2.1-develop:

• https://github.com/magento/magento2/pull/6257
• https://github.com/magento/magento2/pull/10739

According to my understanding newer PR is a correct one (no reason to forbid "none" translation, valid scenario is described in this issue), thus it would be nice to revert #6257.

Thoughts? Cc: @vrann @miguelbalparda

[magento-engcom-team]

@nowszy, thank you for your report.
The issue is already fixed in develop branch
But we will consider to backport the fix to patch releases

[magento-team]

Internal ticket to track issue progress: MAGETWO-75315

[maksek]

@orlangur, the more correct in 2.2-develop branch. Remove translate="true" from layout and do not translate "none" in template.

[orlangur]

@maksek ok, thanks for sorting this out 👍

[magento-team]

Internal ticket to track issue progress: MAGETWO-80884

[okorshenko]

@nowszy thank you for your report. The issue is already fixed in 2.2-develop branch (PR: #11168 by @maksek ) and will be available in the Magento 2.2.2 release

[magento-team]

Internal ticket to track issue progress: MAGETWO-80770

[magento-engcom-team]

Hi @nowszy. Thank you for your report.
The issue has been fixed in magento/magento2#13532 by @hostep in 2.1-develop branch
Related commit(s):

• 00f29c07cb08921009297594758da79d0850f05a

The fix will be available with the upcoming 2.1.13 release.