By the way: What are in general the pros and cons for using migxLoopCollection vs. Blox vs. getImageList...?
you can also just use migxLoopCollection for all the frontend - stuff.
No need to install another package.
pdoResources of the pdoTools - package should also work great.
[[!migxLoopCollection? &packageName=`sriagenda` &classname=`sriagenda_ses` &tpl=`main_agenda` ]]
[[+ses_title]] <br/> [[+ses_type]] <br/> [[!migxLoopCollection? &packageName=`sriagenda` &classname=`sriagenda_spk` &tpl=`@CODE:[[+spk_fname]] [[+spk_lname]], ` ]] <br/><br/>
[[+ses_title]]
<br/>
[[+ses_type]]
<br/>
[[!migxLoopCollection?
&packageName=`sriagenda`
&classname=`sriagenda_ses_spk`
&joins=`[{"alias":"Speaker"}]`
&where=`{"ses_id":"[[+id]]"}`
&tpl=`@CODE:[[+Speaker_spk_fname]] [[+Speaker_spk_lname]]`
&outputSeparator=`, `
]]
<br/><br/>&tpl=`@CODE:<a href="[[~2? &objectID=`[[+Speaker_id]]`]]">[[+Speaker_spk_fname]] [[+Speaker_spk_lname]]</a>`
[[migxLoopCollection?
&packageName=`sriagenda`
&classname=`sriagenda_spk`
&tpl=`@CODE:[[+spk_fname]] [[+spk_lname]]`
&where=`{"id":"[[!getReqParam? &name=`objectID`]]"}`
]]That worked Bruno! I want to now make the template to be a link now. Would that look something like this?
Note: the Speaker Bio page I created has a resource id of 2
&tpl=`@CODE:<a href="[[~2? &objectID=`[[+Speaker_id]]`]]">[[+Speaker_spk_fname]] [[+Speaker_spk_lname]]</a>`
What would the migxLoopCollection call look like on the bio page? Anything like this?
[[migxLoopCollection? &packageName=`sriagenda` &classname=`sriagenda_spk` &tpl=`@CODE:[[+spk_fname]] [[+spk_lname]]` &where=`{"id":"[[!getReqParam? &name=`objectID`]]"}` ]]
[[!migxLoopCollection?
&packageName=`sriagenda`
&classname=`sriagenda_spk`
&tpl=`@CODE:[[+spk_fname]] [[+spk_lname]]`
&where=`{"id":"[[!getReqParam? &name=`objectID`]]"}`
]]<a href="[[~2? &objectID=`[[+Speaker_id]]`]]">[[+Speaker_spk_fname]] [[+Speaker_spk_lname]]</a>