[MGNLPN-115] Personas app stores personas without properly persiting the name due to jcrName Created: 15/May/14  Updated: 22/May/14  Resolved: 15/May/14

Status: Closed
Project: Magnolia Personalization
Component/s: Personas App
Affects Version/s: None
Fix Version/s: 1.0

Type: Bug Priority: Neutral
Reporter: Philip Mundt Assignee: Roman Kovařík
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLPN-116 Fix persona selection and display in ... Closed
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
Epic Link: Personalisation

 Description   

Whenever there is a special character or whitespace in the name of the persona, this will be replaced by jcr-valid characters (info.magnolia.cms.core.Path#getUniqueLabel?). The proper name however should be maintained.



 Comments   
Comment by Philip Mundt [ 15/May/14 ]
  • You probably forgot to also commit the changes of the bootstrap file(s).
  • Would be cool to add another fallback for the case there's no "name" property and just output the nodeName (jcrName) then (PersonaNameColumnFormatter.java)
Comment by Philip Mundt [ 15/May/14 ]
  • Please add the PersonaNameColumnFormatter in the respective name column
Generated at Mon Feb 12 06:34:27 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.