Aiwa Posted June 9, 2016 Share Posted June 9, 2016 These currently have zero filtering capability on Database fields. These really need to be enhanced so they pull the fields associated with the selected database so you can filter, and sort, on those fields. As it is now, the only way to do this is a custom PHP block that just has a query and feeds the resulting data into a theme template. You can't even use a Pages block template because those are only for plugin blocks. Creating a simple database record feed block with a field filter is proving more complicated than creating, configuring, and populating an entire custom database. Link to comment Share on other sites More sharing options...
Management Lindy Posted June 13, 2016 Management Share Posted June 13, 2016 This is done as part of the Pages sweep... next release-ish. Link to comment Share on other sites More sharing options...
Flitterkill Posted June 13, 2016 Share Posted June 13, 2016 Nice. I was actually just dumping records into a block, setting a stupid large number of records retrieved, and filtering manually in the custom template afterwards. Link to comment Share on other sites More sharing options...
Aiwa Posted June 13, 2016 Author Share Posted June 13, 2016 4 minutes ago, Flitterkill said: Nice. I was actually just dumping records into a block, setting a stupid large number of records retrieved, and filtering manually in the custom template afterwards. For now, you can do it via getItemsWithPermission() and some SQL where / sort / limit. But that's not really straight forward unless you're familiar with Content Items and the method available for them. Link to comment Share on other sites More sharing options...
Flitterkill Posted June 13, 2016 Share Posted June 13, 2016 That's a nice bit of code that.. I just brute forced it with the record feed and filtered out what I wanted. Got the job done. Link to comment Share on other sites More sharing options...
CheersnGears Posted June 13, 2016 Share Posted June 13, 2016 21 minutes ago, Lindy said: This is done as part of the Pages sweep... next release-ish. When you're saying next release-ish, I'm assuming not 4.1.13.... are you talking 4.2 or something still in the 4.1.x line? Link to comment Share on other sites More sharing options...
Management Lindy Posted June 13, 2016 Management Share Posted June 13, 2016 1 minute ago, CheersnGears said: When you're saying next release-ish, I'm assuming not 4.1.13.... are you talking 4.2 or something still in the 4.1.x line? Possibly 4.1.13, but definitely before 4.2. The developers are working off an engineering roadmap with branches for each feature edition or major bugfix. After development review and testing, it is merged into development and later pushed for QA and eventually production. We have the ability to push a release without those additions, so if something major were to come up tomorrow, we could push 4.1.13 to include what's already done and tested and merge in things like this in the next release. So, as it stands, it's slated for 4.1.13, but that can change depending on timing. Link to comment Share on other sites More sharing options...
CheersnGears Posted June 13, 2016 Share Posted June 13, 2016 Thanks for the clarification. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.