No subject

should be initiated by the user - an alert saying "This plugin depends
on plugin X to work, activate this now? [Yes] [No]" where clicking Yes
would activate the plugin using the aforementioned WP functions.

I don't think users would appreciate plugins being activated without
their explicit consent.

-- Alex

Sent from my iPhone

On 10 Dec 2010, at 18:05, Scott Kingsley Clark <scott at skcdev.com> wrote:

> I'll likely be using is_plugin_Activated along with activate_plugin,
> sounds good! Thanks again!
>
> -Scott
>
>
> On Dec 10, 11:28 am, scribu <m... at scribu.net> wrote:
>> On Fri, Dec 10, 2010 at 7:02 PM, Scott Kingsley Clark <sc... at skcdev.com>wrote:
>>
>>> Just checking in here, has anyone here ever attempted to activate
>>> another plugin (or ensure it's activated, if not, then activate it)
>>> within a plugin? For example, when activating Plugin B, the Plugin B
>>> will activate Plugin A first (or if Plugin A is activated, continue;
>>> if Plugin A doesn't exist then send error to browser), then complete
>>> the rest of Plugin B specific activation.
>>
>>> I have the craziest of thoughts!
>>
>> Nah, it's not so crazy. You can use is_plugin_activated() and
>> activate_plugin().
>>
>> Or, just add a header and forget about it:http://wordpress.org/extend/plugins/plugin-dependencies/
>> _______________________________________________
>> wp-hackers mailing list
>> wp-hack... at lists.automattic.comhttp://lists.automattic.com/mailman/listinfo/wp-hackers
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers