You are here: Foswiki>Tasks Web>Item2595 (05 Jul 2015, GeorgeClark)Edit Attach

Item2595: extender.pl fails if plugins are misbehaving

pencil
Priority: Normal
Current State: Closed
Released In: 2.0.0
Target Release: major
Applies To: Engine
Component: Configure
Branches: trunk
Reported By: PaulHarvey
Waiting For:
Last Change By: GeorgeClark
  • Install BlackListPlugin
  • Delete System topic
  • Get "use of uninitialized value on line 150" error (See Item8379)
  • Try to use configure to re-install BlackListPlugin
  • extender.pl fails with this error:

Error: Installer returned errors:

************************************************************
Could not load /srv/www/vhosts/wiki.org/foswiki-test/tools/extender.pl
There was a compile error: Use of uninitialized value in concatenation (.) or string at /srv/www/vhosts/wiki.org/foswiki-test/lib/Foswiki/Plugins/BlackListPlugin.pm line 150.
BEGIN failed--compilation aborted at /srv/www/vhosts/wiki.org/foswiki-test/tools/extender.pl line 147.

Error when trying to eval the file content: This installer must be run from the root directory of a Foswiki installation at (eval 253) line 112.
BEGIN failed--compilation aborted at (eval 253) line 147.


You may be able to resolve these errors and complete the installation from the command line, so I will leave the installed files where they are. 

-- PaulHarvey - 06 Jan 2010

I think this is a more basic problem.

extender.pl creates a foswiki object ($session = new Foswiki($user);) and this fails because the plugin fails. I wonder if we have the mechanism to create a foswiki object with all plugins disabled?

I would think the best we could do is make sure all plugins are disabled when we run in this mode.

BlackListPlugin naturally should fail differently but then another plugin that we have no control over will do the same later.

I am sure we have had this problem for years. The work around as the failing extender also tells the user is a manual reinstall of the plugin. Not a very serious error but if we can get extender to disable all plugins when it runs we get the whole thing a little more robust to people can repair a screwed plugin using configure upgrade.

-- KennethLavrsen - 06 Jan 2010

See also (JQueryPlugin kills configure): Tasks.Item8783

-- PaulHarvey - 27 Mar 2010

ItemTemplate edit

Summary extender.pl fails if plugins are misbehaving
ReportedBy PaulHarvey
Codebase 1.0.8, trunk
SVN Range
AppliesTo Engine
Component Configure
Priority Normal
CurrentState Closed
WaitingFor
Checkins distro:46ffa7aa0ab9
TargetRelease major
ReleasedIn 2.0.0
CheckinsOnBranches trunk
trunkCheckins distro:46ffa7aa0ab9
Release01x01Checkins
Topic revision: r7 - 05 Jul 2015, GeorgeClark - This page was cached on 10 Dec 2016 - 10:08.

The copyright of the content on this website is held by the contributing authors, except where stated elsewhere. See Copyright Statement. Creative Commons License