Hi Bruno;
The following call and projects folder files are working good with my custom package.
I have made various tests using another custom classes and queries and works like a charm.
Thanks a lot for another very useful Extra.
Think we have almost all bases covered with MIGx/MIGXdb/bloX
What if i want a JSON output of this listings instead of templates?
I see myself using it a lot for getting consumable data in native apps and ajax front-end calls.
Maybe is a good option/feature-request to be included in bloX from start?
Of course i can make a task and templates like: outerTpl = '[]' outputSeparator ',' and rows like '{"[[+fieldname]]":"[[+fieldvalue]]"}' but will be more usable and portable if we can add a config setting there and templates then will be ignored and just output raw JSON data.
What do you think?
[[!bloX?
&debug=`1`
&use_custom_prefix=`1`
&packagename=`cms`
&project=`cms`
&component=`cms`
&prefix=`uepa_cms_`
&packagename=`cms`
&classname=`Content`
&titlefield=`content_name`
&task=`json`
&sortConfig=`[{"sortby":"id","sortdir":"DESC"}]`
&where=`{"published":"1","content_category_id":"21"}`
]]
[ed. note: lithiumlab last edited this post 11 years ago.]