possible taxonomy issue with group by

[PodsBot]

possible taxonomy issue with group by submitted via Slack by jimtrue

[kristonovo]

Fetch all events ordered by festival type and then by title

festival pod is a custom taxonomy.
event pod is a custom post type.

// assume we´ve got 6 events and 2 festivals

$params = array('orderby' => 'festival.name, post_title', 'limit' => -1, 'groupby' => 'festival.name');
$events = pods('event', $params)

// output should be
Event 1 (Festival 1)
Event 3 (Festival 1)
Event 5 (Festival 1)
Event 2 (Festival 2)
Event 4 (Festival 2)
Event 6 (Festival 2)

// ... but is
Event 1 (Festival 1)
Event 2 (Festival 2)

After testing a while it seems to work when event gets a pod relationship field targeting festival taxonomy. But only without groupby.

$params = array('orderby' => 'festival.name, post_title', 'limit' => -1);

The downside with this is that the festival relation as a taxonomy couldn´t be maintained anymore via wordpress´ quickedit form (ok, extra plugin could do it)

output is

should be

[sc0ttkclark]

When you group by festival.name means that only one record per festival will be shown.

Sounds like what you really want is to order by year, then festival name, then post title, right?

[jimtrue]

Brought this one over from discussion in Slack #support, we had tested with using Taxonomy and it appeared to be ignoring the orderby taxonomy.name. That's primarily what we're testing as the issue. I'm doing a local test to see if there is an issue with orderby as it relates to associated taxonomy over relationship to taxonomy, because that would be a problem.

Also, making a note to myself that group by should really only be used for summary totals calculations and stuff like that, I'm guessing, if it's only returning one row per group. @sc0ttkclark is this one of those situations where groupby is best paired with 'fields' or 'sql' parameters as well to do proper summary calculations?

[kristonovo]

@sc0ttkclark that´s true. At the beginning I misunderstood the concept of groupby but there is still the behaviour that
$params = array('orderby' => 'festival.name, post_title', 'limit' => -1);
ends up like the output shown in the images. I tried to reproduce this issue with a freshly installed wordpress + pods version. Unfortunately it worked how it should 😀

[jimtrue]

@kristonovo It sorted appropriately? Using just taxonomy like you wanted?

[kristonovo]

@jimtrue within the freshly installed test setup: yes. With my actual project: no. Here I still have to assign a real pod relationship field to achieve the wanted output ... are there any debug steps I could follow to give some more info?

[jimtrue]

@kristonovo That's quite odd. That means something else is 'stepping' on the sort. @sc0ttkclark any suggestions? You could try looking at the malfunctioning sort with the following tacked onto the URL: ?pods_debug_sql_all=1 so we could get an eye on the SQL queries being called and compare them.

Do you have any other plugins running on your malfunctioning version that might be touching taxonomy?

[sc0ttkclark]

@kristonovo what in your screenshot is the "festival.name"?

[jimtrue]

@sc0ttkclark that would be the 2014, 2015

[sc0ttkclark]

Might consider 'orderby' => 'CAST( festival.name AS INT(4) ) DESC, t.post_title' (if you want it 2015, then 2014).

[kristonovo]

I´ll try out with debug url and CAST query soon.