Matrix Version: 5.4.5.1
We have Content Container Templates which contain child asset listings where we need to set the relevant Root Nodes twice - once on the container template and a second time for the child asset listing.
Is there any trick / technique / keyword so that the Asset Listing can pick up the Root Nodes set on the parent Container Template?
I don’t think so.
I’ve started setting the static Root Node for Asset Listings in Content Templates to #1, rather than trying to restrict it. (I also make sure that the fallback behaviour for a missing dynamic root node parameter is “Return empty result”). That way I can’t accidentally forget to update it in sync with the others.
It’s not really providing any benefit anyway. Typically the dynamic root node for the Asset Listing will be sourced from either the Container that has the template, in which case it’s effectively restricted by the template’s root node, or it’s sourced from a Related Asset Metadata Field, in which case it’s limited by that field’s Restricted Root Node.
It’s very tempting to do that - especially if there’s no better option.