[wp-hackers] distinguish plugin options?

[Stephen Rider]

I'm trying to avoid having to create/maintain some kind of ongoing  
master list.  Especially as, in order for users to have the most  
current, they would basically be dinging my servers constantly.

In the long term, it would be nice if WordPress created such a list  
that could exist *within the core download*, so that scripts trying to  
figure out what options are "core" or not could do so easily.

Such a thing would also be handy for people (or plugins) trying to  
clean up old stale data, such as options for plugins they no longer  
have.

Also, aren't there some cases in WP core where there are variable  
option names?  add_option( 'option-'.$x, ...) or similar?

Stephen

-- 
Stephen Rider
<http://striderweb.com/>


On Jan 22, 2009, at 9:57 AM, Glenn Ansley wrote:

> Could you GREP svn trunk for add/update_option and parse the data?
>
> On Thu, Jan 22, 2009 at 10:50 AM, Stephen Rider
> <wp-hackers at striderweb.com> wrote:
>
>> I'm trying to figure out if there's any way to distinguish, in the
>> wp_options table, core WordPress options from options set by  
>> plugins.  The
>> only way I can think to do this is to (shudder) maintain a list of  
>> WP Core
>> options, and if a particular option isn't on that list it must be  
>> from a
>> plugin.
>>
>> That isn't a very good solution because it's fragile and manpower  
>> intensive
>> -- I would have to maintain that list vigilantly and basically  
>> forever....
>>
>> Does anyone else have any suggestion as to how this might be  
>> accomplished?
>>
>> This all relates to my Virtual Multiblog system -- a commenter on  
>> my blog
>> had what I thought was an excellent idea, but I don't see how to  
>> implement
>> it well, unless I can distinguish third-party options from core.   
>> Here's a
>> link to the original discussion:
>>
>> http://striderweb.com/nerdaphernalia/?p=236&cp=1#comment-2133