Item2015: Plugin upgrade does not change plugin module in configure

pencil
Priority: Enhancement
Current State: No Action Required
Released In:
Target Release: n/a
Applies To: Engine
Component: extender.pl
Branches:
Reported By: MichaelTempest
Waiting For:
Last Change By: MichaelTempest
If I upgrade an old TWiki plugin to a newer version that is now a Foswiki plugin, {Plugins}{MyPlugin}{Module} still refers to TWiki::Plugins::MyPlugin. It should be Foswiki::Plugins::MyPlugin.

I can fix this via configure, but this problem trips up admins because:
  1. it is an expert setting and
  2. it should be changed automatically when I upgrade a plugin.

-- MichaelTempest - 08 Sep 2009

Michael,

I think that this can be closed. The config checker for PluginsOrder detects this condition and provides the admin with hopefully a meaningful warning.

The extension install process doesn't do any updates to the LocalSite.cfg. And I suspect that going there will be opening up a rather large effort. Confirmation of changes, CLI vs. Web updates, etc.

Is the checker sufficient?

-- GeorgeClark - 30 Aug 2010

Thanks, George. Yes! That warning will do fine. Changing state to "no action required".

-- MichaelTempest - 30 Aug 2010

ItemTemplate edit

Summary Plugin upgrade does not change plugin module in configure
ReportedBy MichaelTempest
Codebase 1.0.6, trunk
SVN Range Foswiki-1.0.0, Thu, 08 Jan 2009, build 1878
AppliesTo Engine
Component extender.pl
Priority Enhancement
CurrentState No Action Required
WaitingFor
Checkins
TargetRelease n/a
ReleasedIn
Topic revision: r3 - 30 Aug 2010, MichaelTempest
The copyright of the content on this website is held by the contributing authors, except where stated elsewhere. See Copyright Statement. Creative Commons License    Legal Imprint    Privacy Policy