Thanks for the information, unfortunately, this does not work when the
core model needs to be accessed in a @PostConstruct method, since at
that time (that is, when adapting to the CustomModel) the core model
member is null. Still searching for a solution for this problem.
@Jörg_Hoh The subnodes are created dynamically, since we want each
subnode to be editable in the editor on the author. The requirement is
that it should be possible to override the data retrieved via the
search. For example, an image is rendered for each item. It should be
possible to override the image of the item with some custom cropping or
adding an alternative image. That is one use case why we created a
resource by default, so the editor can select each item and each image
and edit them in...
Hi, thanks a lot for your answer. Yes, correct. This is exactly the
problem we are facing. Since dynamically creating sub-nodes can be done
on the author, this also works as long as the page is rendered on the
author instance (the sub-nodes will be created) and then publishing the
page, since the sub-nodes will also be copied. Regarding the
requirements, the main advantage of using a list component vs using a
rich text is that the entries can be queried and retrieved dynamically.
For example, "l...
We are working on a solution to what we call the "pagelist", which is a
custom component based on the "list" core component.Using the custom
component it is possible to either render a fixed list of pages or
search for pages dynamically (for example based on tags). This part can
be done quite easily.The challenge we are facing, however, is that it
should be possible to edit each item individually. That is, it should be
possible to edit each list item individually in the editor (for example,