Updating the program

#773

The program does not update itself. It only reports that a new version is out, and you have to install it by hand — this is a deliberate decision: nobody replaces the files on the computer the machines are driven from in the middle of a shift.

How the program reports a new version

Every few minutes the program asks the server for the number of the current version and compares it with its own. If the one on the server is newer, the update check caption starts blinking in the window header. The current version is always visible there too, in the line under the name.

Nothing is downloaded or launched by itself: the blinking caption is a signal, not an installation process.

How to update

  1. Close the program.
  2. Download the fresh archive from the admin panel — the section described in the article How to download the program.
  3. Unpack it into a new folder, not over the old one.
  4. Move the routes file, the file with the number of days and the database file (the .db extension) over from the old folder, if you want to keep the order history.
  5. Check the settings: the orders working folder, the schedule, the conversion parameters. The key and the server address are already written into the new archive.
  6. Start the program and press «Check now» — make sure the cycle goes through and the files are copied.

If something has gone wrong, the old folder is still in place — you can go back to it and sort things out without hurrying.

What is worth checking before an update

  • there are no orders in work in the queue — wait for the end of the current cycle;
  • there are no unfinished operations on the «Issues» tab;
  • you know where the old folder is and it will not be deleted by backup automation.

If there is an updater.exe next to it

This is a leftover of the old update mechanism for the console mode. The program window does not use it. There is no need to run it by hand: it is capable of closing the program and replacing the whole folder, and if the connection breaks during unpacking it may leave the installation in an unusable state.

Background modes

The downloading and conversion modes launched as a service do not update themselves either. They have to be stopped, the program files replaced, and then started again.