[MAGNOLIA-6101] N2B doesn't support multi-value properties Created: 02/Mar/15  Updated: 19/May/22  Resolved: 19/May/22

Status: Closed
Project: Magnolia
Component/s: node2bean
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Daniel Kasmeroglu Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File stacktrace.txt    
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:

 Description   

I've attempted to develop a custom trait which is basically an enum. For example:

flintstonemember

{ fred, wilma, barney, betty, pebbles, bambam }

For the field definition I'm using the OptionGroupFieldDefinition . This definition is pretty basic and configured as followed:

  • trait.rule: multiselect = true
  • trait.value: multiselect = false

The next step is to create a page variant and choose an audience. Selecting the custom trait flintstonemember now allows me to select multiple values (as multiselect = true).
Doing so causes a failure within the Node2Bean component which leads to the attached stacktrace.

The bottom line is that the translation of Node2Bean cannot deal with multiple values (I already talked to Ondrej about it).

Even though I know how to get around this I consider this an error due to the fact that I don't do anything weird here.

Please confirm this issue or explain why I'm wrong in such a basic scenario.

Best regards

Daniel Kasmeroglu



 Comments   
Comment by Jan Haderka [ 02/Mar/15 ]

For such custom trait, you also need to write N2B transformer if you want to store allowed values in multivalue property.

Comment by Roman Kovařík [ 19/May/22 ]

Hello,

This ticket is now marked as closed due to one of the following reasons:

  • A long period of inactivity
  • Uses an old or Beta version of an application, module, or framework that we no longer support
  • The issue is no longer reproducible or has been fixed in later versions

If you are still facing a problem or consider this issue still relevant, please feel free to re-open the ticket and we will reach out to you.

Thank you,
The Magnolia Team

Generated at Mon Feb 12 04:11:19 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.