Item13359: Crash in Configure/Query.pm after installing extension

Installed GenPDFPrincePlugin, Install runs fine, but then configure crashes:

Can't call method "encodeValue" on an undefined value at /var/www/data/Foswiki-1.2.0/lib/Foswiki/Configure/Query.pm line 550.
at /var/www/data/Foswiki-1.2.0/lib/Foswiki/Configure/Query.pm line 550.
Foswiki::Configure::Query::wizard(HASH(0x8ed2238), Foswiki::Configure::Reporter=HASH(0x900f0d8)) called at /var/www/data/Foswiki-1.2.0/lib/Foswiki/Plugins/ConfigurePlugin.pm line 150
Foswiki::Plugins::ConfigurePlugin::__ANON__(Foswiki=HASH(0x885c548), Foswiki::Contrib::JsonRpcContrib::Request=HASH(0x8f8b160), Foswiki::Response=HASH(0x885c5f8), undef) called at /var/www/data/Foswiki-1.2.0/lib/Foswiki/Contrib/JsonRpcContrib/Server.pm line 169
Foswiki::Contrib::JsonRpcContrib::Server::__ANON__() called at /usr/lib/perl5/vendor_perl/5.20.1/Error.pm line 419
eval {...} called at /usr/lib/perl5/vendor_perl/5.20.1/Error.pm line 411
Error::subs::try(CODE(0x8ff2e28), HASH(0x8ff7540)) called at /var/www/data/Foswiki-1.2.0/lib/Foswiki/Contrib/JsonRpcContrib/Server.pm line 183
Foswiki::Contrib::JsonRpcContrib::Server::dispatch(Foswiki::Contrib::JsonRpcContrib::Server=HASH(0x8eaaa58), Foswiki=HASH(0x885c548)) called at /var/www/data/Foswiki-1.2.0/lib/Foswiki/Contrib/JsonRpcContrib.pm line 48
Foswiki::Contrib::JsonRpcContrib::dispatch(Foswiki=HASH(0x885c548)) called at /var/www/data/Foswiki-1.2.0/lib/Foswiki/UI.pm line 374
Foswiki::UI::__ANON__() called at /usr/lib/perl5/vendor_perl/5.20.1/Error.pm line 419
eval {...} called at /usr/lib/perl5/vendor_perl/5.20.1/Error.pm line 411
Error::subs::try(CODE(0x804deb8), HASH(0x885c168)) called at /var/www/data/Foswiki-1.2.0/lib/Foswiki/UI.pm line 500

Reported by padraig_lennon on irc. Similar issues with other extensions that add Spec.

The extension is usable after installation. Ignore error and refresh configure, and the spec is merged. Configuration settings for the new extensions can then be defaulted.

-- GeorgeClark - 07 Apr 2015

This is symptomatic of the other problems I fixed recently, it can safely be closed no-action.

-- CrawfordCurrie - 20 Apr 2015

Commenting is disabled while not logged in