Hotfix: important updates
For supported versions (see Product EOL), it is possible to apply important updates (hotfix) without necessarily updating vtenext to the latest version.
Updating versions often cannot be done immediately due to code customizations or staff training requirements.
We have therefore introduced a new tool that allows you to install stability and security improvements for installations that cannot be updated immediately.
These hotfixes include performance improvements, impactful bug fixes, security patches, etc., and it is therefore recommended to apply them immediately.
From 25.02.2 the notification and installation of hotfix is integrated into the update system in Settings. For previous supported versions they are available via the vteUpdater script.
Installing hotfix using vteUpdater
The vteUpdater script supports hotfix application from version 1.64 so to update it to the latest version go to the root folder of vtenext and run the command:./vteUpdater.sh --force-upgrade
The simplest way is to launch the vteUpdater with the --hotfix parameter (or -x) that will search for, download and install the available hotfix for the installed version:./vteUpdater.sh -x
It is also possible to manually specify the patch to install:./vteUpdater.sh --hotfix=ID
Where ID is the ID of a hotfix, for example: "2887_2926/hotfix_20250701.tgz"
To see all available hotfix for the installed version, use the --list-hotfix option, which also shows the hotfix ID and status (installed, blocked, or not installed):./vteUpdater.sh --list-hotfix
You can also block a specific hotfix if it shouldn't be installed automatically (e.g., because it's incompatible with existing custom code):./vteUpdater.sh --block-hotfix=ID
To unblock it:./vteUpdater.sh --unblock-hotfix=ID
If a hotfix causes problems, you can remove it with the following command, and the overwritten files will be restored with the previous ones:./vteUpdater.sh --revert-hotfix=ID
NOTE: If the hotfix also ran scripts after copying the files, what the script did is unknown, and the changes made by the script will NOT be reverted.
Before applying the hotfix, the script checks that the files it will overwrite have not been modified. If necessary, it lists these files and then stops. In this case, we recommend checking for differences, applying the hotfix anyway, and reapplying the changes to those files. To force the hotfix without checking the files, use the --skip-file-check option:./vteUpdater.sh --hotfix --skip-file-check