The plugin does support filtering of Custom Fields of the type “Post Title (Post ID’s)”. What is the label you’re using for the column? Can you confirm that this label does not show up with a dropdown in the posts overview?
Yes, I can confirm that the label does not show up with a dropdown in the posts overview.
I have a post type “Work Images” that can be associated with two other post types, “Series” and “Exhibitions”.
In the settings for the admin columns for Work Images, I have Series and Exhibitions both set this way: (I’ll just show it for Series)
Type – custom field
Label – Series
Width – default
Custom Field – series
Field Type – Post Title (Post ID’s)
Before –
After –
Enable Filtering – Yes
Enable Sorting – Yes
The sorting works but no dropdowns appear. I have filtering with dropdowns working on other field types on another custom post type.
In the Advanced Custom Fields setting for the series and exhibitions fields they are set to Relationship type and return Post IDs.
Thanks,
Kathy
Thanks for all the information! Could you post the settings you have used in Advanced Custom Fields for these two fields?
Sure!
For the Series field in the Work Images post type…
Field Label – Series
Field Name – series
Field Type – Relationship
Field Instructions –
Required – No
Return Format – Post IDs
Post Type – series
Filter from Taxonomy – All
Filters – Search
Elements – Featured Image, Post Type
Maximum Posts –
Conditional Logic – No
For the Exhibitions field in the Work Images post type…
Field Label – Exhibitions
Field Name – exhibitions
Field Type – Relationship
Field Instructions –
Required – no
Return Format – Post IDs
Post Type – exhibition
Filter from Taxonomy – All
Filters – search
Elements – Featured image, post type
Maximum Posts –
Conditional Logic – No
So I was starting to think it might have something to do with the fact that I have a custom post type that’s the same as a custom field – series, but for exhibitions it’s plural for the custom field and singular for the custom post type.
Neither dropdown shows up.
Thank you!
All right, I’ve been able to reproduce this problem. It is caused by using the relationship field, which stores multiple entries as serialized data in the database. Filtering does not support this, as we cannot properly search through serialized data. We have plans to implement this in the future, but for now, it simply won’t work. I’m sure this was not the answer you were hoping to get, but I hope this at least answers your question :-).
Thanks for looking into this Jesper. At least I know there’s not an issue with the way I had things set up.
That would be great if the capability is there at some point!
