It's sort of misleading for sure. FMS consists of a lot of different parts and they don't all get updated in each revision. The db engine is still at v2 and that's what you see through the get function.
thanx Wim - i don't ge that - it just violates all i know/value.
there was un update for FMS13v1 once which was a revision update before v2 .. - so why then just stick with FMS13v2 and name them Rev.2 Rev.3 etc ..
it is all inconsitent IMHO - and in DB business i am super annoyed by inconsistant stuff ..
it is not just misleading - it is a problem bug - it breaks our server-blacklist function.
We upgraded to fms13.0v4 so that we can run server-side scripts, because fm13.0v2 does not deal with multi-file server-side-scripts properly.
We added "fms13.0v2" to our FMS-blacklist, which stops our software from being opened on v2, as this is not compatible with our serverr-side-script functionality.
... but because of this bug v4 looks like v2 - we have no way of distinguishing the goodies from the baddies!
It's a bug!