I have in mind a patch for http://svn.gregarius.net/trac/ticket/320, but wanted to validate the design here first... It seems to me that instead of storing an array of arrays for the hook name -> functions list, we could add a third array. So we'd have plugin function name -> plugin file name -> function list, an array of array of arrays. The rss_plugin_hook function could then take an optional second parameter - the name of the plugin file who's hook needs calling. Finally, then, in admin/plugins.php we would call rss_plugin_hook for each plugin that's being activated or deactivated. This does not yet give us a way to use a standard plugin hook for configuration of the plugin. This is currently done with a ///Configuration section in the metadata, because we want to require some action (activate, or click configure button) before a new plugin is permitted to execute code. I suppose it would be nice to come up with a design for ticket 320 that resolved this inconsistency as well, but I can think of nothing. Barring any objections, i'll likely start work on a patch late this week. -kz