[MGNLPN-676] Missing labels for country.valueField.options Created: 22/Jul/22  Updated: 05/Jan/23

Status: Reopened
Project: Magnolia Personalization
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Antony Hutchison Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File screenshot-1.png     PNG File screenshot-2.png    
Issue Links:
relation
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Epic Link: AuthorX Support
Team: AuthorX

 Description   

It appears that labels for many countries in country.valueField.options.* are missing.

Steps to reproduce

  1.  create /modules/personalization-traits/traits/country/valueField/options/fr
  2.  Use label =country.valueField.options.fr
  3. create a persona and edit traits to add a country trait
  4. observe the country names in the list


Expected results

It shows country.valueField.options.fr

Actual results

It should show "France" to authors using the English language interface.

Workaround

We could add these labels to our light-modules, but it makes more sense if it's included in Magnolia in all the supported translations. Alternatively we could forego translated labels and just put 'France' in the label.

Development notes

We've observed this with IE, KW, FR. It works with the traits included with Magnolia as expected. We could not find where these labels are defined so we don't have a definitive list of allowed label names.



 Comments   
Comment by Laura Delnevo [ 10/Aug/22 ]

The related Helpdesk ticket has been closed as fixed, because there's a workaround

Generated at Mon Feb 12 06:39:59 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.