You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Inside a client project we added a CPT "financing" via this plugin. Also added a taxonomy "financing-connection" to connect another CPT "industries" to the posts inside the "financing" CPT.
At first it look all fine.
But the term selection on the post editor of "industries" was not working.
Requesting the term via the REST-API is returning an empty body as the post editor requests it:
/wp-json/wp/v2/financing-connection?context=view&per_page=100&orderby=name&order=asc&_fields=id%2Cname%2Cparent&_locale=user
Checking the REST endpoint without the _fields parameter is returning fine. But the core adds the fields parameter.
Stepping through the request let's me find that if I unhook the "fill_empty_meta_keys_with_default_values" method the request including the _fields parameter works fine.
After renaming the taxonomy to "connected-financing" everything works.
The text was updated successfully, but these errors were encountered:
Inside a client project we added a CPT "financing" via this plugin. Also added a taxonomy "financing-connection" to connect another CPT "industries" to the posts inside the "financing" CPT.
At first it look all fine.
But the term selection on the post editor of "industries" was not working.
Requesting the term via the REST-API is returning an empty body as the post editor requests it:
/wp-json/wp/v2/financing-connection?context=view&per_page=100&orderby=name&order=asc&_fields=id%2Cname%2Cparent&_locale=user
Checking the REST endpoint without the _fields parameter is returning fine. But the core adds the fields parameter.
Stepping through the request let's me find that if I unhook the "fill_empty_meta_keys_with_default_values" method the request including the _fields parameter works fine.
After renaming the taxonomy to "connected-financing" everything works.
The text was updated successfully, but these errors were encountered: