The set_post_thumbnail function uses the metadata functions to set the featured image. You have two actions to hook into that process: EDIT: The action hooks are now defined different Thanks @dalbaeb! update_postmeta, before the data is written into the database. Previously update_post_meta updated_postmeta, after the data is written into the database. Previously updated_post_meta SECOND EDIT: … Read more
You are correct; WordPress will not update custom database columns using wp_update_post() or wp_insert_post(). Instead of creating custom database columns, consider using post meta and/or taxonomy APIs. If you must altar the wp_posts table, you will need to update your custom columns on your own and you may run into issues with various other plugins … Read more
See add_meta_box which has a lot of demo code for working with meta fields. Here is the most relevant part for you: /* Do something with the data entered */ add_action( ‘save_post’, ‘myplugin_save_postdata’ ); /* When the post is saved, saves our custom data */ function myplugin_save_postdata( $post_id ) { // First we need to … Read more
Turns out WordPress do not recommend updating GUID thus its disallowed. But we can update it using sql query: global $wpdb; $wpdb->update($wpdb->posts, [‘guid’ => $newGUID], [‘ID’ => $postID]);
Today, I was trying to insert an imported data into WordPress. I was using wp_insert_post to insert data, and it threw the following error: WP_Error Object ( [errors] => Array ( [db_update_error] => Array ( [0] => Could not update post in the database ) ) [error_data] => Array ( ) ) My friend said … Read more
It appears to be a bug, but one that can be hacked around each time it happens with about 2 seconds of work. This wordpress forum thread: If you’re using Chrome, right-click on the greyed-out “Update” button and select “Inspect Element”. You will see something to the likes of: <input name=”save” type=”submit” class=”button button-primary button-large … Read more
Answer couldn’t be simpler. As pointed out by Otto at the wp-hackers list, problem was me not setting post_date_gmt when using wp_update_post(). Final code looks like this: if ( $post_date < strtotime( “tomorrow” ) ) { $status=”publish”; $newpostdata[‘post_status’] = $status; $newpostdata[‘post_date’] = date( ‘Y-m-d H:i:s’, $post_date ); // Also pass ‘post_date_gmt’ so that WP plays … Read more
That message is a result of your server throwing a 503 error and the WordPress Heartbeat API catching that error. See https://core.trac.wordpress.org/ticket/25660 for the background on the fix that WordPress introduced to save offline edits. Things to check on your computer are if WAMP is actually running when you’re getting this message (check the status … Read more
I guess it should work . As long as $id is available things are easy. <?php if (empty($items)) { $ret .= ” ‘No new videos.'”; $postid = $post->ID; //Supply post-Id here $post->ID. wp_update_post(array( ‘ID’ => $postid, ‘post_status’ => ‘draft’ )); } else foreach ( $items as $item ) : ?> Give it a shot.
It depends on where you’re using this. Is global $post giving you the specific post that you want to update? Your WordPress update post code looks right to me, but is the if-statement valid, and is $post->ID yielding the correct int?