[wp-hackers] Re: [wp-svn] [4530] branches/2.0/wp-includes/functions-post.php: Include post_content_filtered in queries to comply with MySQL strict mode.

[Matt Mullenweg]

m at wordpress.org wrote:
> +			post_content_filtered = '$post_content_filtered',
> +			(post_author, post_date, post_date_gmt, post_content, post_content_filtered, post_title, post_excerpt,  post_status, comment_status, ping_status, post_password, post_name, to_ping, pinged, post_modified, post_modified_gmt, post_parent, menu_order, post_mime_type, guid)
> +			('$post_author', '$post_date', '$post_date_gmt', '$post_content', '$post_content_filtered', '$post_title', '$post_excerpt', '$post_status', '$comment_status', '$ping_status', '$post_password', '$post_name', '$to_ping', '$pinged', '$post_date', '$post_date_gmt', '$post_parent', '$menu_order', '$post_mime_type', '$guid')");

As far as I can tell, $post_content_filtered isn't set anywhere before 
it's used in post.php. Possible hole, let's do the isset() trick and 
also put apply_filters on it so if people wanted to use this field with 
a plugin they could easily.

-- 
Matt Mullenweg
  http://photomatt.net | http://wordpress.org
http://automattic.com | http://akismet.com