troyhallisey

Thanks for the response. No I am not really stuck. I have already added

if ( isset( $_REQUEST['post_format'] ) && $_REQUEST['post_format'] != -1 ) {
	set_post_format($post_id, $_REQUEST['post_format']);
}

to my callback before I need to use get_post_format. This just checks if the post format var is set and not equal to the No Change option from the select menu. It seems like this is such as easy solution that I am not sure why its not designed like that to begin with.

Also I am using save_post because I am using a metabox to save some custom data and then sync that data and WP core data to an external database when the post is published or updated (and Bulk Edited). Though I agree with you that I can’t possibly be the first person ever needing to use get_post_format in a save_post callback.

The Codex says that save_post is always called after the post is updated as well, but since this is obviously not always the case (as in post_format and also the sticky status just below wp_update_post in the referece), it seems misleading to say that. If its by design it should be at least referenced in the codex as an exception.

Thanks. The email address is one set up with my hosting plan and therefore has the same domain as the site. I only discovered the bounce backs after setting up and logging into the Horde system. Yeah, I don’t think it has anything to do with the plugin either, other than the possibility that I set it up wrong, but I don’t think that I did because it worked fine with MAMP. I’ll just wait for the web host to get back to me. Thanks for your help.