-
1. Re: Looping and storing into arrays
Robert Bell (Bosweb) Nov 5, 2014 9:39 PM (in response to Liam Dilley)Those would be great.
What I'd really like to see, is basic filters on module_ tags, so we can reduce the set of returned elements before the infernal pagination limit is hit. (Wasn't this already mentioned somewhere?)
E.g., in your example, only the first x hundred webapp items can be looped over to test for classification/name/whatever. We should instead be able to say something like {module_webapp collection="myitems" where="item.classificationName EQ foobar"}, so we'll get matching items even though they wouldn't have appeared in the first page of unfiltered results.
-
2. Re: Looping and storing into arrays
Liam Dilley Nov 5, 2014 10:00 PM (in response to Robert Bell (Bosweb))Well Rob, you have {module_data... So if you want to go even further You can turn to that and you can defiantly do the where. I think bringing that to all modules would be some serious overkill work, you would be basically replicating that functionality.
That is how I am classing _data - This is your hardcore module to use when you want to do some serious s*** but as I have said in other threads, We should not be turning to that all the time when we just need something like categories in list view. That would also be over kill in those situations.
But then when you do use _data it would be good to get some results, map it to an array and then use that for something else.



