Beta 7: Query builder - no taxonomy

Beta
#1

Will you be adding Categories and Tags into the Query Builder? At the moment there’s no obvious way of laying out a specific group of posts or products using a category or tag.

I found something called Term but not sure what that’s doing.

1 Like
#2

Yes, I’m sorry about that. We were hoping to get that in for this beta but will need a bit more time. The Looper Provider will have a “Filter” control that lets you scope in which posts you need by category, author, etc.

#3

Not sure if this is in the plans already but could there also be the option to exclude certain posts?

#4

Yes! You’ll be able to include or exclude by ID.

1 Like
#5

So I realize we’re actually talking about two different things here. In the next patch you can:

  • Filter the results of the Looper Provider type “Query Builder” by taxonomy
  • Setup a Looper Provider to “Current Post Terms”. This will allow you to loop over the categories/tags of a post and use the Terms Dynamic Content.
#6

Hello!
Will there also be a frontend filter option? eg. display certain taxonomy names and and after click only show posts that have that taxonomy assigned?

1 Like
#7

Hi @BuzzStory,

I’m sorry, presently we don’t have any items to filter from the front end. You would need to create links to different categories.

#8

Hello @alexander,

Would this be possible:

  • Develop a UI for filtering outside of Pro
  • Use that UI to set the parameters for the Query Builder on a Looper
  • See the page update as the filters are modified

Thanks, Bill.

#9

Yes, technically that would be possible if you were doing something that updated query params in the URL. It wouldn’t support a realtime/AJAX/javascript filtering system.

There are some low level filters in the looper system that can help with this kind of custom development

  • Filter: cs_looper_provider_query_args will let you adjust the query built by the Recent Posts, Query Builder, and Query String provider types.
  • Filter: cs_resolve_looper_provider can be used to supply a custom looper provider type. Unfortunately we don’t have a way in the UI to represent this yet, so it’s all done behind the scenes.