It seems that the action save_post gets fired when sending a post to the trash… Therefore, my custom metadata save function was being activated with no $_POST data to send thru it. To circumvent this, I wound up adding a nonce to the save function. function wpg_testimonial_author() { global $post; $custom = get_post_custom($post->ID); $testimonial_author_name = … Read more
The sticky posts are saved as an array of post IDs in the wp_options table. Hence, $stickies = get_option( ‘sticky_posts’ ); $stickies[] = $post_id; update_option( ‘sticky_posts’, $stickies ); will make the post in question sticky. EDIT: Even better, the core provides functions to stick and unstick posts (had to have ’em). stick_post( $post_id ); unstick_post( … Read more
You JOIN two elements both with the same table. When you need to join one table more than once, you need to make each join unique by giving the table alias. When WP makes the whole query, it takes that into account, but you have added your own code that doesn’t do that. So, first … Read more
The way your code is setup is just wrong, you are making two database calls for each custom field and if you have between 2-30 fields like this then that means you make over 60 calls to the database which can be done with a single call using get_post_custom() for ex: $custom_fields = get_post_custom($post->ID); for … Read more
A standard WordPress schema “sync” via dbDelta() will only add indexes, not drop them. Same goes for fields. We never touch the storage schema either, so it’d be the default for MySQL (which in latest versions is now InnoDB). On the face, a comment_id_meta_key index makes perfect sense. But when you look at how WordPress … Read more
The problem is that the function update_field from ACF works a little bit different from update_post_meta. Can you see it? update_post_meta( $post_id, $meta_key, $meta_value, $prev_value ); update_field( $field_key, $value, $post_id ); If you use update_post_meta you should in my opinion use get_post_meta to get the meta. If you use update_field you should use the_field or … Read more
For NEW post type ‘post’ use draft_to_publish action hook: function fpw_post_info( $post ) { if ( ‘post’ == $post->post_type ) { // echo ‘<pre>’; print_r( $post ); echo ‘<br />’; // $meta = get_post_meta( $post->ID ); print_r( $meta ); echo ‘</pre>’; die(); // your custom code goes here… } } add_action( ‘draft_to_publish’, ‘fpw_post_info’, 10, 1 … Read more
There’s a private filter you can (but shouldn’t) access: Defined in wp-includes/revision.php: /** * Filter the list of fields saved in post revisions. * * Included by default: ‘post_title’, ‘post_content’ and ‘post_excerpt’. * * Disallowed fields: ‘ID’, ‘post_name’, ‘post_parent’, ‘post_date’, * ‘post_date_gmt’, ‘post_status’, ‘post_type’, ‘comment_count’, * and ‘post_author’. * * @since 2.6.0 * @since 4.5.0 … Read more
That’s because the fields weren’t set then. Note: The »Autosave« process/request also doesn’t save them. Use the values from $_POST instead for your “new_to_publish” action. EDIT: Do NOT forget to escape and properly sanitize input data! Else you will open a security hole.
They were both introduced in version 2.9, but were done so in different files. update_postmeta went into /wp-admin/includes/post.php While… update_{$meta_type}_meta went into /wp-includes/meta.php It was only later that update_postmeta was shifted into /wp-includes/meta.php. So I believe it was for backward compatability, where by because the update_postmeta hook was always receiving the value of maybe_serialize() then … Read more