Upgrade to Matomo 5.4.0 #29
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Helpful background context
Upgrade the Docker container to run Matomo 5.4.0 so that we can enable the new CustomReports plugin.
How can a reviewer manually see the effects of these changes?
A log in to the UI for dev-matomo will show that it is running version 5.4.0.
The updated container was deployed to Dev1. It did require a database upgrade (
./console core:upate) that took only a few seconds to update tables:root@ip-172-32-1-149:/var/www/html# ./console core:update *** Update *** Database Upgrade Required Your Matomo database is out-of-date, and must be upgraded before you can continue. Matomo database will be upgraded from version 5.3.2 to the new version 5.4.0. *** Note: this is a Dry Run *** ALTER TABLE `matomo_user_token_auth` ADD COLUMN `ts_rotation_notified` DATETIME NULL; ALTER TABLE `matomo_user_token_auth` ADD COLUMN `ts_expiration_warning_notified` DATETIME NULL; ALTER TABLE `matomo_user` ADD COLUMN `ts_last_seen` TIMESTAMP null DEFAULT null; ALTER TABLE `matomo_user` ADD COLUMN `ts_inactivity_notified` TIMESTAMP null DEFAULT null; UPDATE `matomo_user` u JOIN ( SELECT SUBSTRING_INDEX(o.option_name, 'UsersManager.lastSeen.', -1) AS login, o.option_value AS last_seen FROM `matomo_option` o WHERE o.option_name LIKE 'UsersManager.lastSeen.%' ) AS userData ON u.login = userData.login SET u.ts_last_seen = CONVERT_TZ(FROM_UNIXTIME(userData.last_seen), 'SYSTEM', '+00:00'); DELETE FROM `matomo_option` WHERE option_name LIKE 'UsersManager.lastSeen.%'; *** End of Dry Run *** A database upgrade is required. Execute update? (y/N) y Starting the database upgrade process now. This may take a while, so please be patient. *** Update *** Database Upgrade Required Your Matomo database is out-of-date, and must be upgraded before you can continue. Matomo database will be upgraded from version 5.3.2 to the new version 5.4.0. The database upgrade process may take a while, so please be patient. Executing ALTER TABLE `matomo_user_token_auth` ADD COLUMN `ts_rotation_notified` DATETIME NULL;... Done. [1 / 6] Executing ALTER TABLE `matomo_user_token_auth` ADD COLUMN `ts_expiration_warning_notified` DATETIME NULL;... Done. [2 / 6] Executing ALTER TABLE `matomo_user` ADD COLUMN `ts_last_seen` TIMESTAMP null DEFAULT null;... Done. [3 / 6] Executing ALTER TABLE `matomo_user` ADD COLUMN `ts_inactivity_notified` TIMESTAMP null DEFAULT null;... Done. [4 / 6] Executing UPDATE `matomo_user` u JOIN ( SELECT SUBSTRING_INDEX(o.option_name, 'UsersManager.lastSeen.', -1) AS login, o.option_value AS last_seen FROM `matomo_option` o WHERE o.option_name LIKE 'UsersManager.lastSeen.%' ) AS userData ON u.login = userData.login SET u.ts_last_seen = CONVERT_TZ(FROM_UNIXTIME(userData.last_seen), 'SYSTEM', '+00:00');... Done. [5 / 6] Executing DELETE FROM `matomo_option` WHERE option_name LIKE 'UsersManager.lastSeen.%';... Done. [6 / 6] Matomo has been successfully updated!Includes new or updated dependencies?
NO
What are the relevant tickets?
Developer
Code Reviewer
(not just this pull request message)