Open danielcharrua opened 1 week ago
I get the same issue on my website with the following setup:
8.1.23
6.5.5
v3.2.2
I can also confirm custom field values were returned in the REST API endpoints in the previous Pods version v.3.2.1
.
Maybe it has something to do with this new feature? https://github.com/pods-framework/pods/pull/7285/commits/7b2322b9842e8d1e5dcb715a884ce88b8f466ecf
I did a bit of snooping around and I suspect something goes wrong at this point:
While this setting is set to true
in my Pods admin interface, the value of $can_use_mode_has_value
is false
or null
-ish, thereby restricting read access to all custom fields.
Apparently I had to set every individual Pod's field's Read via REST API
value to true
. I did not have to do this before. It's kind of a breaking change in that sense and begs the question why the release notes did not mention this.
@danielcharrua Can you confirm this works for you as well?
@sc0ttkclark Could you maybe mention or reference this issue in the release notes of v3.2.2
? :-)
Looking at this for the release this week
Noticed the same issue today after upgrading to 3.2.2. Tried @drikusroor's fix but in my case the relationship field isn't returned in the API response even after setting the "Read via REST API" field to "Yes"
Description
The custom fields are not shown on the REST API when globally options are set.
In previous versions I had global options enabled to show all fields (read and write) and this was working OK.
I do some basic testing and activate this options per-filed and they appeared. Maybe something was broken in global options por the pod.
Version
3.2.2
Testing Instructions
Screenshots / Screencast
No response
Possible Workaround
No response
Site Health Information
No response
Pods Package