Hide
Another issue already mentions the useless use of a container type.
to this container are related 'portalpagesnodes', which are sorted by a order_number field in those objects themselves. The role between them is childppnn whateever that may stand for.
The rest of the world would use a 'posrel' relation in stead. Then, the actual contain is stored in 'simplecontents' which is relate to the last portalpagesnodes without any order:
<mm:relatednodescontainer path="simplecontents" searchdirs="source">
<mm:constraint referid="today" field="online_date" operator="LESS" />
<mm:constraint referid="today" field="offline_date" operator="GREATER" />
<mm:relatednodes>
(this is already cleaned up by me).
So, if you link more than one, the contents is shown in random order.
I simply do not understand why it has to be this difficult.
Drop containers. Use posrel. What's hard about that?
Show
Another issue already mentions the useless use of a container type.
to this container are related 'portalpagesnodes', which are sorted by a order_number field in those objects themselves. The role between them is childppnn whateever that may stand for.
The rest of the world would use a 'posrel' relation in stead. Then, the actual contain is stored in 'simplecontents' which is relate to the last portalpagesnodes without any order:
<mm:relatednodescontainer path="simplecontents" searchdirs="source">
<mm:constraint referid="today" field="online_date" operator="LESS" />
<mm:constraint referid="today" field="offline_date" operator="GREATER" />
<mm:relatednodes>
(this is already cleaned up by me).
So, if you link more than one, the contents is shown in random order.
I simply do not understand why it has to be this difficult.
Drop containers. Use posrel. What's hard about that?
Sub-task
Open
Major