Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

Sort components in parsys

Avatar

Level 3

Hello everyone

I was wondering if there is a standard way of having the components inside of the parsys sorted in some kind of way (preferably by creation date), or if anyone has some pointers on where to start looking into this, without having to change the parsys itself quite a lot (this is because I don't want to mess anything up in case there is a new version of AEM where the parsys might change).

Kind regards

 

1 Accepted Solution

Avatar

Correct answer by
Level 4

Interesting.

The parsys wasn't made with this in mind because the idea is to give the Authors the flexibility to move around the resources inside via a visual GUI.

The need sounds like you are creating pages and or other resources that you want displayed in a list. I can think of like blog posts or something like that.

I would suggest creating a component that has some back end functionality that will build out a list of the resources you are trying to display and then feed them in whatever shape or form you are trying to display them at to the front end component. Separate out the logic to collect the content/resources from the display of the content/resources. This is all assuming its a specific type of resource that is being placed into the parsys/container and not just any component the author has access to.

View solution in original post

1 Reply

Avatar

Correct answer by
Level 4

Interesting.

The parsys wasn't made with this in mind because the idea is to give the Authors the flexibility to move around the resources inside via a visual GUI.

The need sounds like you are creating pages and or other resources that you want displayed in a list. I can think of like blog posts or something like that.

I would suggest creating a component that has some back end functionality that will build out a list of the resources you are trying to display and then feed them in whatever shape or form you are trying to display them at to the front end component. Separate out the logic to collect the content/resources from the display of the content/resources. This is all assuming its a specific type of resource that is being placed into the parsys/container and not just any component the author has access to.