The german (core) developer Dominik Schilling/ocean90 has released a pretty nice, simple and small plugin to encounter (part of) this problem. Instead of adding a complex AJAX save process, that would just make it harder to work with even handlers and such (de- & re-registering them), he just added a position marker, that allows WP … Read more
The hook you’re looking for is created_{$taxonomy} but there’s a another issue. I think the biggest flaw in the logic is putting both states and cities in the same taxonomy. You’ll never be able to differentiate between the two terms ( which is the city and which is the state ). This opens the user … Read more
This is because the first time you go round the loop $post is the current post. But the second time you go around the loop, $post has not changed. The same thing happens the 3rd, 4th, 5th, etc Because the $post variable is the current post of that page, not the post you’ve just saved/inserted, … Read more
save_post Runs whenever a post or page is created or updated, which could be from an import, post/page edit form, xmlrpc, or post by email. Action function arguments: post ID and post object. Runs after the data is saved to the database. above paragraph is quoted from WP Codex. so you cannot use this hook … Read more
I know this has already been answered, but I felt as if it wasn’t 100% real clear what the actual solution was. Here’s my answer to add some clarification. He’s right… You can’t flush rewrite rules on save_post, because that action hook is fired AFTER the init action hook has been fired. As you know, … Read more
When a post is created/edited from the admin, edit_post() is called. This function simply collects all the $_POST arguments and passes them to wp_update_post(). wp_update_post() then does some more logical checks and passes the data along to wp_insert_post(). wp_insert_post() calls sanitize_post(), which does all the heavy duty sanitization. So, yes, wp_insert_post() is the correct way … Read more
function disable_save( $maybe_empty, $postarr ) { $maybe_empty = true; return $maybe_empty; } add_filter( ‘wp_insert_post_empty_content’, ‘disable_save’, 999999, 2 ); Because wp_insert_post_empty_content is set to true, WordPress thinks there is no title and no content and stops updating the post. EDIT: An even shorter variant would be: add_filter( ‘wp_insert_post_empty_content’, ‘__return_true’, PHP_INT_MAX -1, 2 );
This might work for you as well. It scans the post, then pulls in the image set as ‘featured’. If that doesn’t exist, it returns the first image attached to the post. If there isn’t one, it looks for any image in the post; if that’s not there, it grabs a YouTube screenshot. Put this … Read more
The “save_post” action is only called when we actually changed something in the post page form. If we just press the update button, without changing anything, the “save_post” action is not called. This is important if we are editing a custom post type where we had custom meta boxes. If we rely on the “save_post” … Read more
add_action has a priority parameter which is 10 by default, you can increase that to load your function late. Change add_action( ‘save_post’, ‘do_custom_save’ ); to add_action( ‘save_post’, ‘do_custom_save’, 100 ); Now the priority is to set to 100 and will load quite late and will allow other function associated to load before this function is … Read more