This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
possible taxonomy issue with group by #3570
Comments
Fetch all events ordered by festival type and then by title festival pod is a custom taxonomy.
After testing a while it seems to work when event gets a pod relationship field targeting festival taxonomy. But only without groupby.
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) |
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? |
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 Also, making a note to myself that |
@sc0ttkclark that´s true. At the beginning I misunderstood the concept of groupby but there is still the behaviour that |
@kristonovo It sorted appropriately? Using just taxonomy like you wanted? |
@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? |
@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: Do you have any other plugins running on your malfunctioning version that might be touching taxonomy? |
@kristonovo what in your screenshot is the "festival.name"? |
@sc0ttkclark that would be the 2014, 2015 |
Might consider |
I´ll try out with debug url and CAST query soon. |
@sc0ttkclark
|
Maybe without |
@jimtrue 1
2
3
4
5
6
7
|
@sc0ttkclark |
Are you entirely sure you've provided the correct information about the output? Can you provide the PHP you're using to list the content? |
The longer it takes to find a solution the more I worry it might be my own fault 💃
... and this is the setting in event pod: |
Any chance you'd be willing to provide a login for us to get into your Pods Admin area to look into this for you? You can send it privately on our Slack (http://pods.io/chat/) or through this form: https://pods.io/help/ |
Yes, I could prepare a dev environment. Would need some time though. In the meantime I tested one other thing:
params always the same: Might it be possible that multiple taxonomy relations are interfering with orderby? They are kept in database as far as I know. Even if I remove the relation. |
Following up on this, it wasn't an issue with Pods as much as it was an issue with MySQL. For whatever reason, when you did an ORDER BY a joined field, it wouldn't order the results correctly. If you added Further digging will be required by a MySQL expert to determine why this happens and how we can mitigate it in the future. |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
possible taxonomy issue with group by submitted via Slack by jimtrue
The text was updated successfully, but these errors were encountered: