Item637: The dependencies of plugins, which are themselves plugins, don't seem to be taken into consideration when installing a plugin

The dependencies of plugins, which are themselfes plugins, seem to to be taken in consideration when installing a pluigns. So you easily can install a plugin, without its "plugin deps" ( not CPAN ), you get no error.

This will confuse users, getting no error, "feeling" an automated installation.

It could be, that my dependencies are in wrong systax, i use

This is my DEPENDENCIES file example

DBConnectorPlugin

Anybody can reproduce/confirm this?

• EugenMayer - 02 Jan 2009

I took the freedom to edit the summary. Could you please specify a Plugin which depends on DBConnectorPlugin (I don't use it aside from beta-testing, so I don't know of any)?

If this is the case, I'm not sure whether we can do anything about it now apart from inserting some kind of red box in the plugin description stating the dependencies (AFAIK there's no means to queue plugin installs w/ accompanying user dialogs in configure; also, it should be made clear that all required plugins have to be activated as well once the plugin in question is activated -- this is a non-trivial extension and thus requires a feature proposal topic...)

(not lowering the priority in order to have this reviewed again)

• MarkusUeberall - 02 Jan 2009

TopicSpecificNavigation is one of them. I think we dont need a autoinstall-plugin-deps feature if it has not be there, but we should change the way the users gets noticed, that something is missing.

-- Foswiki:Main.EugenMayer

If this was not a feature in TWiki is will not be a release blocker in Foswiki either.

But would be a nice enhancement.

I change this to enhancement.

• KennethLavrsen - 02 Jan 2009

If I understand this request, it's probably fixed in Foswiki 1.1. Dependencies of type Perl are auto-installed recursively by both the Shell and the Web extension installer. The Shell installer can also optionally attempt to install CPAN dpendencies.

-- GeorgeClark - 03 Dec 2010

I also understand that this was implemented a long time ago. We have the problem with only first plugin being upgraded that may affect this feature. But if so it is fixed in SVN and will be released in 1.1.3.

I have not planned 1.1.3 yet. If things go as fine as until now a xmas release to "clean the air" is on my mind.

No need to keep this open.

-- KennethLavrsen - 03 Dec 2010