You’re running the query twice and passing the result of the first query to the second query. Give this a try. You might also consider using the update function from wpdb instead of running an arbitrary query because it doesn’t look like you’re doing any data sanitization or nonce checks. If you do want to … Read more
If your problem is: I want to send email if a postmeta of a post is changed to the expected value Why do yous ask for: How can i get the List of post id on bulk edit? This is a typical x/y problem: when you have a problem, ask how to solve that problem, … Read more
You hook the tr_change_show_title to a filter inside the function itself, that can make a infinite loop. All the stuff removing/adding actions and filters inside the functions should be deleted; instead check if the post data should be updated or not. In your case you should check if the title has the value you desire … Read more
I’m going to post this as an answer, because it worked for me: function my_awesome_func ($post_id, $post, $update) { //update the value we need early update_post_meta($post_id, ‘my_meta_key’, $_REQUEST[‘my_meta_key’]); $newValue = get_post_meta($post_id, ‘my_meta_key’); } add_action( ‘save_post_my-custom-post-type’, ‘my_awesome_func’, 10, 3 ); You could also simply use the value of $_REQUEST[‘my_meta_key’] directly if that works, but for my … Read more
You can hack this plugin code by changing ‘create_draft‘ option ‘no’ to ‘yes’ into plugin.php ‘get_default_import_options‘ method(Approx line no. 1013). I’m not tested this hack, try it your own risk.
It all depends on how your “custom fields” are saved. If you store the values as post meta then you would have to call the update_post_meta function to update them on wp_insert_post_data. In the example below Im setting the post meta “my_meta_key” with the string value “my_meta_value”. function save_my_post( $content ) { global $post; if( … Read more
Since you already mentioned that you are using these codes, I assume they both work for you. Now, I have combined them for you into a single function that updates the metadata after a post is published: function set_date_difference($post_id){ // Get the value of the first field $date1 = get_field(‘date_start’, $post_id, false ); $date1 = … Read more
You can hook into post_updated action, if you want to access the post’s data after it’s been published. This hook passes the post’s ID, inundated post object, and updated post object. add_action( ‘post_updated’, ‘update_event_date’, 10, 3 ); function update_event_date( $post_id, $post_after, $post_before ){ $post_type = get_post_type( $post_id ); $event_datee = get_post_meta( $post_id, ‘_EventStartDate’, true ); … Read more
It looks to me like save_post doesn’t work the way you currently have your add_action. According to the Codex, you need to run your function on save_post and check the post type in the function. function get_film_data( $post_id ) { if ( get_post_type($post_id) == ‘film’ ) { // If this is just a revision, don’t … Read more
Try this code: function cf_description_to_content($post_ID){ $data = get_post_meta( $post_ID, ‘wiloke_listgo_my_custom_fields’, true ); // Put whatver description you want assign to the description field $data[‘description’] = $_POST[‘wiloke_listgo_my_custom_fields’]; update_post_meta( $post_ID, ‘wiloke_listgo_my_custom_fields’, $data ); } add_action(‘save_post’, ‘cf_description_to_content’, 100, 1);