Null meta keys

Hi @jdearana,

Which endpoint are you using?

Let me know,
Kevin.

Hi @jdearana,

Are you able to add a new meta field to articulos just to see if it works?

Also, could you look into the database at a single articulos' post meta fields? Is the data clean? Are they saved consistently?

You could also try some of our filters:

The filter wp_rest_api_controller_api_property_value will allow you to hook into the value of each meta field. You could use this filter for testing (try echo’ing out some values, or returning a test string). The filter has three arguments: the value of the post meta field, the ID of the post, and the name of the field. Let me know if you need any more information on this filter.

I am not sure what’s going on so any ideas as to what’s different between your newly-created CPT and the articulos CPT would help!

Cheers,
Kevin.

Hi @niteshvaghani,

I am not sure what’s going. There are a few things to try though.

1. Do you have any other custom post types? Can you enable them using our plugin and check if their post meta is accessible via the API?

2. How are you making this custom post type? Are you using a plugin? Are there any REST API settings coming from the plugin? It may be that our plugin is conflicting with another one.

3. You can try using the filter I mentioned above. I will copy that paragraph here.
The filter wp_rest_api_controller_api_property_value will allow you to hook into the value of each meta field. You could use this filter for testing (try echo’ing out some values, or returning a test string). The filter has three arguments: the value of the post meta field, the ID of the post, and the name of the field. Let me know if you need any more information on this filter.

Sorry for the delay it’s been a busy day.

Cheers,
Kevin.

Hi @niteshvaghani,

So let’s focus on your filter function using the wp_rest_api_controller_api_property_value.

For testing, that function should look something like:

add_filter( 'wp_rest_api_controller_api_property_value', 'testing_rest_api_controller', 10, 3 );

function testing_rest_api_controller( $meta_value, $post_id, $post_meta_name ) {
    var_dump( $meta_value );
    var_dump( $post_id );
    var_dump( $post_meta_name );
}

Now let’s take one of your meta field’s where you know what the value should be and add a get_post_meta() call for that specific meta field’s value. I’ve added this line in the following function. Replace 'example_meta_key_name' with the meta key you’d like to test with. Does this return the correct value? Is the value returned from this call different than the value returned as the first parameter (meta_value)?

add_filter( 'wp_rest_api_controller_api_property_value', 'testing_rest_api_controller', 10, 3 );

function testing_rest_api_controller( $meta_value, $post_id, $post_meta_name ) {
    var_dump( $meta_value );
    var_dump( $post_id );
    var_dump( $post_meta_name );
    var_dump( get_post_meta( $post_id, 'example_meta_key_name', true ) );
}

Let me know if that approach makes sense and what the results are.

All the best,
Kevin.

Hi @yclaes,

Do you know if the original meta keys that are causing problems have dashes in them?

Also, is it a problem if you’re required to rename the meta fields?

Let me know.

Cheers,
Kevin.