Codepress Admin Columns doesn't see Pods' table-based custom fields (meta keys)

[pglewis]

An older version of Codepress Admin Columns (1.4.9) appears to recognize table-based custom fields added by Pods. Integration broke somewhere.

[pglewis]

https://github.com/pods-framework/pods/blob/f2c903/classes/PodsMeta.php#L413

Pods specifically intercepts the cpac-get-meta-by-type filter from CodePress Admin Columns in order to feed the plugin the list of fields in the case of table-based storage for CPTs (SELECT DISTINCT meta_key ... will not discover the fields when using table storage for the post type). This filter no longer appears in a search of the code for Admin Columns and I don't think it has been around since somewhere back in the 1.x versions.

[pglewis]

An immediate closer looks shows there are a series of filter hooks for CPA 2.x just above the referenced line. A breakpoint in cpac_meta_keys_get() never gets hit for a custom post type, however. I don't think we're hooking the right thing.

[realdadfish]

I'm still on Pods 2.5 and while this bug is still open (and the milestone is set to 3.0) the above patch ebecfba seem to have made it already into this very version of the Pods framework - at least I can see it in my installation.

I'm reporting this obviously because custom fields are (again?) not visible even with this change. I am using codepress' admin columns 2.3.2.

[Shelob9]

@tommyd3mdi Thanks for the report. I am putting this back into 2.X for more research.

[pglewis]

This is "can't reproduce" for me at the moment. The user interface is not 100% intuitive for custom fields, but the following works for me in testing with both table and meta based storage on a custom post type:

• Click "Add Column"
• For "Type", choose "Custom Field" in the "Custom" section

Selecting "Custom Field" will modify the UI and provide a new drop down for the actual custom fields.

I'm going to punt this from 2.5.3 for now, let me know if this is still an issue and if there is something different I need to do to reproduce the problem.

[Ramoonus]

@markoheijnen

[pglewis]

Closing this since we've not been able to get any information to reproduce it.