Upgrade 3.16

Version: 3.16

Version required: 3.10 and above

A few words from the author - version features

Technical support regulations. Please be reminded that we only support, advise and troubleshoot bugs within the last 3 versions (respectively 3.16, 3.15 and 3.14). For earlier versions, only recommended updates to the latest builds are.

Upgrade. Recommended to have two instances of the system. A separate live one and a separate test one. On the test one you can periodically update the database from the live system and perform updates to make sure everything is working, familiarise yourself with innovations or identify things that have stopped working for you.

Our Telegram group for mutual communication between clients: https://t.me/usersideeu and a channel for news: https://t.me/userside

If you are upgrading from version 3.11 and earlier - check out the page: Upgrade 3.12

If you are upgrading from version 3.12 and earlier - check out the page: Upgrade 3.13

If you are upgrading from version 3.13 and earlier - check out the page: Upgrade 3.14

If you are upgrading from version 3.14 and earlier - check out the page: Upgrade 3.15

Read the "Requirements" section of the installation instructions to determine what changes need to be made to the operating system environment to work relative to its current state. Version 3.16 requires the installation of the RabbitMQ message broker, and the installation and configuration of Supervisor to manage background processes, which may require Python to be updated.

Using the automatic installer, perform an upgrade. In case of an error during the upgrade process or if the installer did not complete correctly, run the installer in recovery mode:

sudo -u www-data php userside_install.phar repair

If you are working with the UserSide API - there have been a lot of changes to it due to the redesign including the employee/operator/personnel system. Check out the information on the Versions 3.16 page (especially section 3.16dev2)

The notification system has been completely redesigned. If you are using the Imobis SMS service, you will need to change the authentication method in the USERSIDE settings to token authentication after the upgrade. If you have self-described message delivery services, make sure to copy your service file from the erp/services/notification/custom directory to a spare directory before the upgrade and after the upgrade copy it from the spare directory to the erp/modules/Notification/Domain/MessageService/custom directory that will appear after the upgrade to 3.16. If you do not have any self-described services (CustomUrl is not a self-described service, but a service supplied with the system), you do not need to do anything.

If you use additional tabs in the subscriber card - use "employee_id" and "employee_hash" instead of "operator_id" and "operator_hash" parameters

List of Changes: view

Performing the upgrade: instruction