I have a CPT made with pods called “CD” and a custom taxonomy called “Year” attached to it. I used to use orderby=”year.name ASC”, for example, to order CD’s by Year but it’s not working anymore, I guess since 2.8 update but not sure. Am I doing something wrong or something did change?
Looks like this may be related to an issue we are looking at in the upcoming Pods 2.8.2 release. It was affecting a different use-case but it’s the same exact area so that’s why I think they may be related to the same regression bug.
Here’s the bug I filed for this: https://github.com/pods-framework/pods/issues/6230
Can you go to the place on your site where this would normally display and add this to your URL while logged in as an admin?
That will cause Pods to output the queries it uses on those find() requests for the page.
If you can find on the page where that spot would be, there should be a textarea with what the query used was. Can you provide that in a reply here to better help me understand this individual case?
I guess this is it. Just FYI, in this case, it’s an artist page (“artista” post type, in portuguese) that displays artist’s CDs (“disco” post type) by Year (“ano” tax).
WHERE ( (
ID= ‘2513’ ) AND (
post_type= ‘disco’ ) AND (
post_statusIN ( ‘publish’ ) ) )
Two of those joins are removed by a fix in Pods 2.8.2 (they join but don’t appear to alter the query results).
I’m not seeing anything other than those two that are out of the ordinary for the query other than that. To confirm, your taxonomy name is “ano” and this is a taxonomy associated to the CPT.
And the CDs are all set as published for their status?
Yes, taxonomy name is “ano” and it’s associated with the CD (“disco”) CPT with Pods. Yes, all the CDs are set as published.
You may also want to try out Pods 2.8.2 ahead of the release — https://github.com/pods-framework/pods/archive/refs/heads/release/2.8.2.zip — and let me know if it solves your issue entirely as that could save us both time knowing it’s fixed.
I installed 2.8.2 but I guess it didn’t resolve my issue. At least, not with old code that was working before 2.8.
The Pods 2.8.2 release went out today and you can update to that whenever you are ready. I believe your issue was addressed but I did fix a similar one yesterday.
Let us know if the update does resolve your problem as planned.
Looks like we posted pretty close to each other 🙂
Let’s try to get additional information about your issue created as a new bug on our GitHub at https://pods.io/submit/ and we can help you over there to debug and figure out what’s going wrong.
Pods 2.8.3 is out now and you can try once again to confirm that we solved your problem. I know it’s been a bit of back and forth here but I did revisit the
Pods::find()in 2.8.3 and I think it may resolve your problem here.
I just updated to 2.8.3 and I’m afraid it didn’t work for me, at least not with the same shortcode as it used to. I’ll submit it to GitHub later so we can look further. btw, I entered Pods’ Slack Community but didn’t have the chance to look around just yet.
More effort went into Pods 2.8.4 to resolve this issue with associated taxonomies specifically. It finally resolved the issues I kept seeing on our own Pods site with associated taxonomy usage exactly like what you’re using. After applying the update it resolved that problem entirely for us.
Pods 2.8.4 is now out and has a fix that addresses the issue reported here.
Well, I just updated and still not working for me. Guess I’m doing something wrong then, but can’t figure it out what.
Could you create a full bug report on GitHub so we can further look into this issue?
Closing topic here!
- The topic ‘Orderby custom taxonomy still works?’ is closed to new replies.