[Feature Request] Some Log Entry or UI Notice/Warning of the Client & Server version Mismatch

[Da-Geek]

Simple as the $Subject says :-)

If a user is running a Mismatched client, that could cause issues with the smooth operation of the Client.

For instance, If the Client is too New and the server side has not been updated, some features may not work as expected.
or the other way round, so if a Client is a very old version, again it may not report things to the server as expected.

Maybe even a new field in the user properties that shows the last time & version of a Acars connection (that could be
shown in the Pilot Profile to show a successful connection from a client)

This Feature Request is related to/requires issue #14

[nabeelio]

I like the posting of the version to the client's profile, that's a good one. I don't have a version for the web module, per se. Because it doesn't need to be updated every time. But I design it so that if the client has some settings that require the web module to be updated, it has sane defaults and won't break.

Lemme think on it

[FatihKoz]

If a user is running a Mismatched client, that could cause issues with the smooth operation of the Client.

This is really important, back in days we had a problem just because of this. The client was not updating itself, and there were no indications of updater failing. As expected user was "thinking" there were no updates and he is using the latest version. But in fact he was way behind and had troubles loading flights etc.

The root cause was his service provider, blocking connections. Nothing related with acars + phpvms or with the va itself.

A version check somewhere independent from acars update checks may come in handy for this kind of weird situations.