[wp-hackers] Re: Plugin to post source code needs testing

[Bas Bosman]

Another option would be to store the GeShi result in the
"post_content_filtered" field, which is still part of the posts table.

Whenever somebody requests the content, you return the filtered content by
hooking into the required filters.

If you deactivate the plugin, the original (unprocessed) content is once
again used. And you can even use the deactivate hook to clean up your
post_content_filtered data. (And genereate it for already existing posts
on activate)

Regards,
Bas Bosman (Nazgul)

> Only thing to keep in mind is if you ever switch to another plugin, you'll
> have your old posts looking different.
>
> On 9/19/07, Otto <otto at ottodestruct.com> wrote:
>>
>> On 9/18/07, Matt <speedboxer at gmail.com> wrote:
>> > On 9/18/07, Otto <otto at ottodestruct.com> wrote:
>> >
>> > > Oh, and it just occurred to me that the WP-Syntax plugin could
>> pretty
>> > > easily be modified to work at post creation time instead of post
>> > > display time. This would mean that GeSHi would only have to run
>> > > through the code one time, when you publish it.
>> > >
>> >
>> > Then if you disable the Plugin, all your code would still be
>> highlighted...
>>
>> True, but that seems pretty desirable to me. Why would I want my posts
>> to look like crap?
>> _______________________________________________
>> wp-hackers mailing list
>> wp-hackers at lists.automattic.com
>> http://lists.automattic.com/mailman/listinfo/wp-hackers
>>
>
>
>
> --
> Computer Guru
> Director,
> NeoSmart Technologies
> http://neosmart.net/blog/
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>