kaf at szub.net
Wed Jan 4 03:40:46 GMT 2006
Ryan Boren wrote:
> Please don't do this. If someone is using a replacement cache, this
> won't work. Plus, these are the sort of things that make plugins so
> fragile to core changes.
(Important note: I'm not angry, frustrated or anything of the sort. I
am just someone in search of answers, and maybe even solutions.)
What makes plugins fragile is when changes are made to the core with
no warning. Having $cache_categories available on category queries
worked. I'm sure there was good reason to pull it, and with other
methods I'm not arguing for its return, but we're getting to where
users can plan on any plugins of any complexity to break when a new
WP release hits. Even if it follows coding guidelines and implements
nothing but WP calls.
Is there a resolution to this? With the somewhat free form method of
coordinating development and disseminating information on core mods
which could break existing code, I just don't know. Certainly part of
it involves the participation of those of us working on plugins, but
it'd sure be nice not to have to test each of my plugins with every
large, and sometimes even incremental, upgrade. And with no guarantee
what worked in tonight's build will do so tomorrow, it can be a daily,
time-consuming effort if one wants to keep up.
Maybe I just need to vent--no, I'd prefer some slightly easier way of
managing my harem of plugins to make sure they're ready for WordPress
version Next. Sitting on my hands until after a release, waiting for
the flood of bug reports to drop in my inbox isn't a smart way to go
about it, but it's starting to look attractive...
>> The codex has sample code using $cache_categories, so how would one
>> know not to use it? http://codex.wordpress.org/Category_Templates
> Good grief. That never should have been documented and needs to change.
Obviously it needs to change, but why should it not have been there?
It was in the core since (at least) 1.2.2. I know because I have a copy
set up for testing! It's there in 1.5.x. I can't find a comment or note
or mention of it having been deprecated, or requiring emergency surgery,
Seriously, why does it require a Charlie Brown response?
More information about the wp-hackers