Using Pro 5.6.0 btw. Not sure if I should post this in the PRO section instead.
OK – not sure why, but ditching add_post_meta() / update_post_meta() in favour of ACF’s own update_field appears to work fine!
add_action( 'load-post-new.php', 'wpse8650_post_new' );
function wpse8650_post_new()
{
add_action( 'wp_insert_post', 'wpse8650_wp_insert_post_default' );
}
function wpse8650_wp_insert_post_default( $post_id )
{
if ($_REQUEST["new_post_prefill"] == "yes")
{
update_field('type', "Short conversation", $post_id );
update_field( 'customer', "Imaginary customer name", $post_id );
update_field('parent_post', 1234, $post_id );
}
}
I just created another post object field in the same form and that works fine: I can do a add_post_meta( $post_id, 'temporary_second_post_object_field', $_REQUEST['my_post_id'] ); and the field assumes that value with no problems!
I suppose deleting the original field and recreating it might work, but I can’t really afford to do that, I’ve got hundreds of values in it that I’d have to painstakingly restore somehow…. also I suppose this might happen again any time.
Could this be some obscure bug, then?
