[wp-hackers] post_content_filtered

[denis at semiologic.com]

Sounds like a good idea indeed. I was just surprised to find no hook anywhere to
call it in the WordPress code. At the moment, the only occurence of it is in the
install script.

I would have imagined finding something somewhere like:

if ( $post->post_content_filtered )
  // bypass post_content filters

and like:

apply_filters( wherever_relevant, update_post_content_filtered )

at other places. But leave as is, I presume, as there is room to cache things
differently from a site to another.

Speaking of which: If I make a plugin to fill the field every so often on a
semi-static basis rather than on a per-modification basis, is there a way to I
disable the apply_filters call on the_content altogether?

D.

Quoting Matt Mullenweg <m at mullenweg.com>:

> denis at semiologic.com wrote:
> > I noticed this 'post_content_filtered' column in the posts table. It
> doesn't
> > appear to be used anywhere in wp. Is this a remnant of a past version of
> wp,
> > something a plugin installed on my site, something else...?
>
> It can be used by plugins for caching expensive post content
> transformations.
>
> --
> Matt Mullenweg
> http://photomatt.net  | http://wordpress.org
> http://pingomatic.com | http://cnet.com
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>




----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.