[wp-hackers] Plugin Management issue...

[David Chait]

this sounds like you really want add_filter_after or something like that...
;)  But yes, you are also screwed if someone else writes any other plugin
that does

I have some similar stuff I'm converting to plugins, one that needs to be
EARLY in the_content processing (maybe before your spellchec!), one that
wants to be after 'general' processing (i.e., I don't mind curly quote
conversions, etc.), but certainly before any tags start getting added.  The
first is my custom CG-Inline processor, which is how I do my magic floated
images/thumbnails, amazon items, and page and perma links.  The second is my
dropcap code, which while I've had turned off for a while now, I think I'll
convert it 'just in case'.  I'm trying to move ALL my CHAITGEAR code over to
plugins -- well, at least where it is physically possible, and doesn't have
to be hacked. ;)

I know there's a priority parameter for filters too -- maybe those
priorities need to have some distinct 'constant' ranges set?

-d

----- Original Message ----- 
From: "Alex" <nessence at gmail.com>
To: <hackers at wordpress.org>
Sent: Tuesday, June 29, 2004 11:49 AM
Subject: Re: [wp-hackers] Plugin Management issue...


> You can also do crazy stuff like (what I probably shouldn't be doing):
>
> # remove texturizer b/c preg doesn't like it
> remove_filter('the_content', 'wptexturize');
>
> # do our spell check - make sure it's last (eg, after acronyms if it's
there)
> # this way recognized acronyms don't end up as typos
> add_filter('the_content', 'do_spell_check');
>
> # put the texturizer back - after spell checker
> add_filter('the_content', 'wptexturize');
>
> texturize places things in the content dynamically. therefore, I
> wanted my plugin executed beforehand because I just wanted the content