Pods: BETA 2.7 - Extended post and page types pods not available through the REST API.

Created on 4 Dec 2017  路  7Comments  路  Source: pods-framework/pods

The issue resides in the REST API not showing the PODs extensions (for pages and posts). I have meta_title, meta_description, and hero_image_text. Using the stable version 2.6 they show fine in the api. When updating to the 2.7 they stop working. Cleared PODs cache, didn't help.

An easy way to understand what happens is to compare my staging env which is using 2.7 beta: http://reactcasino.staging.wpengine.com//wp-json/wp/v2/posts. And searching for meta_. No results found. As mentioned above these fields are added with PODs.

In production (using 2.6) http://reactcasino.wpengine.com//wp-json/wp/v2/posts. Search for meta_ again and you'll see the fields.

The custom fields show in the posts and pages (under both versions) only the API seems to be affected.

Running Wordpress 4.8.4 (can update staging if you think 4.9 can fix it).

Reproduced Bug

Most helpful comment

Found

All 7 comments

Both environments are exactly the same, the only difference is the version of PODS.

I can verify this as an issue, was able to reproduce instantly. Extended posts, added one field, Enabled REST API 'show all fields'. 2.6.11 the field shows in the REST API output (/wp-json/wp/v2/posts) in 2.7rc1, it doesn't.

I can confirm Custom Posts/taxonomy don't seem to have this issue, just 'post' extended. 'users' extended is also fine. Testing 'page' and the others very quickly.

Confirmed Extended Page also loses pods custom fields in 2.7rc1

Looking

Found

Fixed

Was this page helpful?
0 / 5 - 0 ratings

Related issues

sc0ttkclark picture sc0ttkclark  路  4Comments

devont3 picture devont3  路  3Comments

Kpudlo picture Kpudlo  路  4Comments

wpstudio picture wpstudio  路  6Comments

jcampbell05 picture jcampbell05  路  5Comments