2020-12-08, 13:04
@DaveBlake,
You are absolutely right. I had missed that he was using a folder and not a filter type node. I was too focused on the rules part.
@Offsprin. Dave's explanation above is spot on. You should consider it when choosing the type of node to create. I would say if it is in your library use filter. If it is not scanned into the library, the use a folder node. My apologies for not noticing that you were using a folder node.
With that said, the node below should give you the desired list. Depending on the size list wanted, you can choose to modify or that have a limit at all.
<?xml version='1.0' encoding='UTF-8'?>
<node order="9" type="filter">
<label>Recent Movies 4K</label>
<content>movies</content>
<match>all</match>
<rule field="path" operator="contains">
<value>movies/4K</value>
</rule>
<limit>25</limit>
<order direction="descending">dateadded</order>
</node>
You are absolutely right. I had missed that he was using a folder and not a filter type node. I was too focused on the rules part.
@Offsprin. Dave's explanation above is spot on. You should consider it when choosing the type of node to create. I would say if it is in your library use filter. If it is not scanned into the library, the use a folder node. My apologies for not noticing that you were using a folder node.
With that said, the node below should give you the desired list. Depending on the size list wanted, you can choose to modify or that have a limit at all.
<?xml version='1.0' encoding='UTF-8'?>
<node order="9" type="filter">
<label>Recent Movies 4K</label>
<content>movies</content>
<match>all</match>
<rule field="path" operator="contains">
<value>movies/4K</value>
</rule>
<limit>25</limit>
<order direction="descending">dateadded</order>
</node>