[wp-hackers] How to check a new plugin?

[Eric Mann]

Would be helpful for other developers and admins yes, but some plug-ins use
a *lot* of hooks and filters.  Creating a list would be needlessly
time-consuming.  When we get down to that, it's just an extra step for
admins and researchers who care to actually crack open the plug-in and look
at in-line documentation.

On Mon, Nov 22, 2010 at 10:32 AM, Bill Dennen <dennen at gmail.com> wrote:

> One suggestion for the plugin directory -- put the onus on plugin
> developers to state whether or not their plugin creates additional
> database tables, and other things. They could list the hooks they use,
> for example.
>
> It could be a short checklist that is displayed alongside the existing
> plugin info in the plugin directory.
>
> Having this info would help you decide whether a plugin is worth it --
> and it would help you troubleshoot problems if they occur.
>
> -Bill
>
> > Read every line of code
> > Test it works.
> > Check it doesn't kill your db servers.
> > Profit
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>