[MAGNOLIA-4732]  There is no utility methods that returns all the properties that are not special, needed when you dont know the name of the properties you want to display Created: 17/Dec/12  Updated: 19/May/22  Resolved: 19/May/22

Status: Closed
Project: Magnolia
Component/s: core, templating
Affects Version/s: 4.5.7
Fix Version/s: None

Type: Improvement Priority: Major
Reporter: Teresa Miyar Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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)
Date of First Response:

 Description   

Either content.getProperties() and contentMap.keyset return all the properties in the node, including the special properties. In the previous API you could call getProperties and it would return all the non special properties. This is needed i.e. multiselect control, when you get the properties as 0,1... you dont know the names. One way could be to prefix this names with the node name like link0, link1 this way you could get all the properties that start with 'link', and the other way would be to provide a method that returns just the non special properties.

Have a look at current method contentMap.keyset, it returns all the properties special an non special and also the special prefixed with @



 Comments   
Comment by Teresa Miyar [ 18/Dec/12 ]

comment from Jan
@Teresa MAG-4732 - getProperties() method returns iterator. You can wrap it in FilteringNodeIterator and @Eric recently committed JcrAndMgnlPropertyHidingPredicate for it to hide all system related properties

But, my problem really is that before you had a 'utility method' that could be used directly in the ftls

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 03:58:30 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.