How to perform an update/upgrade?
Please make sure that the directories
are readable, writeable and executable by the webserver.
This HowTo describes, how to update your current VIMP installation to the latest version (also applies for upgrades e.g. from VIMP Ultimate to VIMP Corporate), including all installed modules.
Always BACKUP your files and database before performing an update!
This article describes how to create a backup.
VIMP update packages have the following nomenclature:
VIMP module update packages have the following nomenclature:
VIMP In-Place Update
Since version 5.0 VIMP can be updated comfortably to a new version via the "VIMP Update" page in the backend.
Please note that only administrators who have assigned the "access backend update" permission can access the in-place updater.
Simply upload the new updater file (vimp.framework-<version>-<edition>-updater.bin) via the file selection box and then start the update. You can still choose to skip creating a backup (not recommended!) and to delete the update file after the update is done.
After the update has started you can see the update progress in the log window. You can save the log afterwards.
If an error should occur during an update, you can easily revert to the last version by restoring the previously created backup.
In this example, we will update VIMP Ultimate [Standard] 4.2.12 to VIMP 4.3.0.
Load the update packages into the VIMP installation directory of your server, e.g. via SFTP or FTP.
As root, change to the VIMP installation directory in the shell (e.g. with Putty) and give the packages permission to run (we assume an installation under /var/www/html in the following):
cd /var/www chmod +x vimp.*-updater.bin
Clear the VIMP/symfony Cache:
Next, execute the update script:
You'll be prompted to enter or confirm the installation path. Default value is the current folder and is written in square brackets [...].
Install path [/var/www/html]:
Just hit Return, if you want to confirm the pre-filled value.
The updater checks the system requirements:
Starting Installer ... >> OK PHP version is at least 7.0.0 (7.4.6) >> OK PHP version is equal or less than 7.4.x (7.4.6) >> OK DOM extension is installed >> OK XML extension is installed >> OK XSL extension is installed >> OK Tokenizer extension is installed >> OK Multibyte String extension is installed >> OK iconv extension is installed >> OK Posix extension is installed >> OK GD extension is installed
>> OK Imagick extension is installed >> OK cUrl extension is installed >> OK mysql extension is installed >> OK mcrypt extension is installed >> OK PDO is installed >> OK PDO mysql driver is installed >> INFO PDO has some drivers installed: mysql, sqlite >> OK MySQL version is at least 5.0.6 (5.5.5-10.4.17-MariaDB) >> OK SourceGuardian extension is installed >> OK php.ini has short_open_tag set to off >> OK php.ini has magic_quotes_gpc set to off >> OK php.ini has register_globals set to off >> OK php.ini has safe_mode set to off >> OK php.ini has session.auto_start set to off >> OK php.ini has file_uploads set to on >> OK php.ini has allow_url_fopen set to on >> OK php.ini has register_argc_argv set to on >> OK php.ini has set memory_limit not equal to -1 >> OK php.ini has set memory_limit greater or equal than 512M >> OK php.ini has set memory_limit lesser than 2G >> OK php.ini has set post_max_size greater or equal than 100M >> OK php.ini has set post_max_size lesser than 2G >> OK php.ini has set upload_max_filesize greater or equal than 100M >> OK php.ini has set upload_max_filesize lesser than 2G >> OK ffmpeg is installed >> OK ffprobe is installed >> OK exiftool is installed >> INFO Version: 4.3.0 (r27301) >> INFO Edition: ULTIMATE >> INFO OS: Linux 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 >> INFO Memory: 63GB Continue? [Y/n]:
As we're updating a running VIMP platform, no ERROR messages should be expected. Confirm with Return to continue.
Now, the new files will be extracted from the package. The updater compares the given database tables with the new ones and always asks you to confirm changes.
... >> update Table channel_user changed >> update Table config changed >> update Table menu changed >> update Table role_permission changed Changes for Database found. Apply? [Y/n]:
Enter Y or press Return to apply the database changes. In case you didn't create a database backup yet, this is the last chance to abort and save your current database.
... >> update Changing table category... >> update Check filesystem for changes >> update File /data/sql/updates.sql changed >> update File /data/sql/upgrade.sql changed Changes for filesystem found. Apply? [Y/n]:
Confirm once again and the update of the framework will be executed.
VIMP is now updated/upgraded and you can access it in the browser under your domain.
Last update on 2021/10/27 by Admin.