Item10374: HistoryPlugin crashes foswiki in Sandbox.pm

I am using Foswiki 1.1.2 with NatSkin. In the Sandbox web I create a topic and also create a second revision. Viewing revisions from the "changed by.." link works fine. When I try to view topic history using the HistoryPlugin in NatSkin (using the oopstemplate), Foswiki dies with the message:

| 2011-02-18T13:00:36Z warning | invalid number argument '1.$rev' %REVISION&vbar;N% at /var/www/vhosts/mavrogenis.com.gr/subdomains/qpm/httpdocs/lib/Foswiki/Sandbox.pm line 388.

looking into the error.log I see a sequel of warnings, first about the ZonePlugin and then about the "invalid number" (the ZonePlugin warnings are coming up all the time - the installation is live for 3 days and the error.log is 1.8Mb, all with ZonePlugin warnings).

| 2011-02-18T13:00:36Z warning | Foswiki::Plugins::ZonePlugin | ZonePlugin is not compatible with your Foswiki version |
| 2011-02-18T13:00:36Z warning | Foswiki::Plugins::ZonePlugin::initPlugin did not return true.
Check your Foswiki warning and error logs for more information.
 |
| 2011-02-18T13:00:36Z warning | invalid number argument '1.$rev' %REVISION&vbar;N% at /var/www/vhosts/mavrogenis.com.gr/subdomains/qpm/httpdocs/lib/Foswiki/Sandbox.pm line 388.

I copied a web from an older installation and viewing topic history with HistoryPlugin produces the same error. After editing a topic, and adding a new revision, using HistoryPlugin to view topic history produces the same error.

When removing the .txt,v file, clicking on the clock icon to view topic history creates a list of all revisions all pointing to the latest revision (the .txt file)

-- StefanosKouzof - 18 Feb 2011

For the ZonePlugin warning, disable ZonePlugin on 1.1.x - the functions added by ZonePlugin are part of 1.1 core and this plugin is no longer used. For the HistoryPlugin issue, changing this task to NatSkin extension. The history plugin works on the default pattern skin.

-- GeorgeClark - 27 Feb 2011

I think at least there should be a reference on the natskin documentation about problems with specific plugins, but I am not sure what the problem is (or even if it is in the natskin), or where to look for it. There are no errors in the logs.

-- StefanosKouzof - 08 Mar 2011

No. Not documenting the bug. The Natskin simply needs to get fixed. And I am sure Michael will do this. He takes good care of his stuff.

-- KennethLavrsen - 08 Mar 2011

I can agree to that. But I even tried the 10440 svn checkout for natskin with no effect.

-- StefanosKouzof - 14 Mar 2011

Can't be reproduced anymore. Seems fixed. Please reopen if the bug still persists in latest releases.

-- MichaelDaum - 24 May 2013

Commenting is disabled while not logged in