MODX Staff
☆ A M B ☆
The current getResources 1.2.2-pl is suffering from that bug (thus driving me crazy while testing all kind of variations etc. Until I found this thread ;-).
That’s definitely a bug; &parents does not currently allow an empty value to be set, and so uses the current page by default. Please enter an issue for this at GitHub so it gets resolved quickly.
[[getResources? &parents=`[[*related]]` &resources=`[[*related]]` &tpl=`relatedTPL`]]
☆ A M B ☆
In the meentime I found something like a workaround: same &parents as &resources
[[getResources? &parents=`[[*related]]` &resources=`[[*related]]` &tpl=`relatedTPL`]]
Does it for me for now but does not work, if the children of [[*related]] are NOT to be included.
☆ A M B ☆
OK, I found another solutions, which works best for me:
Even better: Just select a &parent which definetly does not have any kids, like the error-page or whatever. I &parents does not have kids it delivers an empty result, so it’s being ignored. Perfect!
[[getResources? &parents=`-1` &resources=`23,45,56` &tpl=`relatedTPL`]]
☆ A M B ☆
"9999" is also fine, just like any non existing id. I just liked "-1" a lot bettet, since you will never run into conflicts even if the id is used one day (before the update ;-)
What happens if you set &parents=`99999` ?
The workaround is fine, but the "autofetch id" should not be removed since some user may already be using it. Perhaps a parameter like ’FALSE’ or ’’ (empty) should be possible AND documented. This way, the old users would be happy because their sites won’t break, and the "new" user would be able to do what they intended to do.
It really should work with no &parents parameter, but I haven’t looked at the code.