You are here: Foswiki>Tasks Web>Item1055 (12 Dec 2017, GeorgeClark)Edit Attach

Item1055: Find More Extensions should compare installed version with latest version

Priority: Normal
Current State: Closed
Released In: 1.0.4
Target Release: patch

Applies To: Engine
Component: Configure
Branches:

Reported By: ArthurClemens
Waiting For:
Last Change By: GeorgeClark

The 2 values are not comparable, so there is always the link "Upgrade" even if both versions are the same.

See for instance:

The version is 1.037, but the strings do not match.

The extension has a free form entry in the table. For TablePlugin this is:

|  Plugin Version: | 1.037 (16 Dec 2008) |

and in TablePlugin.pm this is:

$RELEASE = '1.037';

RELEASE is also free form. It would be better to use the automatically assigned VERSION, and write that to the extension table upon building. Then FastReport can read the value from the extension table.

-- ArthurClemens - 17 Feb 2009

Done so far:

Make 'version' and 'installed version' uniform by only comparing the svn revision number, so we do not confuse by using different notations
Show a message "up to date" if both versions are equal (with green background); use pink background for extensions that need upgrading
Updated FastReport to show the proper data (added classification, removed shouldRunOn and testedOn, added compatibility)

Now a number of extensions should be re-published with the correct %$VERSION% string at Version: in the extension topic:

-- ArthurClemens - 01 Mar 2009

See Item1198 for more

-- CDot

ItemTemplate edit

Summary	Find More Extensions should compare installed version with latest version
ReportedBy	ArthurClemens
Codebase
SVN Range	Foswiki-1.0.0, Thu, 08 Jan 2009, build 1878
AppliesTo	Engine
Component	Configure
Priority	Normal
CurrentState	Closed
WaitingFor
Checkins	BlogAddOn:062cae1aad18 distro:309277b130ef
TargetRelease	patch
ReleasedIn	1.0.4