Must have all selected items checkbox ignored in Query Builder for Taxonomies

Hi,

I am trying to set up a Looper Provider based on post categories. I use the Query Builder and have selected two categories under Taxonomies.
As I understand checking “Must have all selected items” should result in filtering posts with both categories assigned. Unfortunately, it is being ignored on my end (pro 4.0.6).

Regards
Marcin

Hello Marcin,

Thanks for writing in! I have tested the Query and it is working. There is a bug in the looper consumer when you use the Grid and Cell element. The Grid should be the looper provider and only cell is needed to be the looper consumer. At this moment, there is a bug in it which I can confirm. I have created a test page on your site using the same Query. I am using the Grid/Cell and the Row/Column layout. Only the Row/Column displays all the correct post items. The one I have added in the Grid is not displaying the items properly. They are stack in front of each other. I have raised this issue to our developers already.

You can check the test page for the Query in the secure note below.

Thank you @ruenel for your reply.
Regardless of the bug with Grig/Cell combination, I cannot make the Must have all selected checkbox to work for me. I have simplified your example a bit and took Row / Column combination only. Here is the list of posts:


3 of them have Category1 assigned and 3 both Category1 and Category2.
As I understand the setting like this:

should result with filtering posts with both categories only. Unfortunately, I all six posts are still visible. Can you please have a look and check once again?

Hello Marcin,

I have investigated the issue further and this is a bug in the query. I will be reporting this issue to our developers so that this can addressed and fixed in the next patch release.

Please bear with us. Thanks.

Don’t want to be a nagger, but it seems the bug was not fixed in 4.0.8 release. As this is the last thing, I need to proceed with my main website to be upgraded (and updated) can you please indicate when the fix can be expected?

Thanks and regards
Marcin

Hi @Marcin_Podwojski,

This one is fixed in the upcoming point release.

Thank you @alexander! I can confirm it works fine in 4.0.9

Regards
Marcin

Ok great! Thanks for confirming with us.

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.