Upgrade Matomo to 3.6.1 or 3.7.0
Closed, ResolvedPublic5 Story Points

Description

Finally thew new 3.6.x Debian packages are out (https://github.com/matomo-org/matomo-package/issues/81) and the 3.7.0 is in preparation as far as I can read. They both contain security fixes for XSS vulnerabilities and upstream suggests to upgrade asap.

Changelog:

https://matomo.org/changelog/matomo-3-6-0/
https://matomo.org/changelog/matomo-3-6-1/
https://matomo.org/changelog/matomo-3-7-0/

elukey created this task.Mon, Nov 19, 7:12 AM
elukey triaged this task as Normal priority.
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptMon, Nov 19, 7:12 AM
elukey updated the task description. (Show Details)Mon, Nov 19, 7:13 AM
elukey updated the task description. (Show Details)
elukey added a comment.Wed, Dec 5, 8:57 AM
*** 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 3.5.1 to the new version 3.7.0.

*** Note: this is a Dry Run ***

ALTER TABLE `piwik_site_setting` CHANGE `idsite` `idsite` INTEGER(10) UNSIGNED NOT NULL;
ALTER TABLE `piwik_plugin_setting` ADD COLUMN `idplugin_setting` BIGINT UNSIGNED NOT NULL PRIMARY KEY AUTO_INCREMENT;
ALTER TABLE `piwik_site_setting` ADD COLUMN `idsite_setting` BIGINT UNSIGNED NOT NULL PRIMARY KEY AUTO_INCREMENT;
ALTER TABLE `piwik_log_profiling` ADD COLUMN `idprofiling` BIGINT UNSIGNED NOT NULL PRIMARY KEY AUTO_INCREMENT;
ALTER TABLE `piwik_access` CHANGE `access` `access` VARCHAR(50) NULL;
ALTER TABLE `piwik_access` DROP PRIMARY KEY;
ALTER TABLE `piwik_access` ADD COLUMN `idaccess` INT UNSIGNED NOT NULL PRIMARY KEY AUTO_INCREMENT;
ALTER TABLE `piwik_access` ADD INDEX index_loginidsite (`login`, `idsite`);
ALTER TABLE `piwik_user` ADD COLUMN `ts_password_modified` TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP;
CREATE TABLE `piwik_report_subscriptions` (`idreport` INT(11) NOT NULL, `token`  VARCHAR(100) NULL, `email` VARCHAR(100) NOT NULL, `ts_subscribed` TIMESTAMP DEFAULT CURRENT_TIMESTAMP, `ts_unsubscribed` TIMESTAMP NULL, PRIMARY KEY ( `idreport`, `email` )) ENGINE=InnoDB DEFAULT CHARSET=utf8;
ALTER TABLE `piwik_report_subscriptions` ADD UNIQUE KEY unique_token (`token`);
ALTER TABLE `piwik_user` CHANGE `ts_password_modified` `ts_password_modified` TIMESTAMP NULL;
UPDATE `piwik_user` SET ts_password_modified = NULL;
ALTER TABLE `piwik_site` ADD COLUMN `creator_login`  VARCHAR(100) NULL;
ALTER TABLE `piwik_goal` ADD COLUMN `event_value_as_revenue` tinyint(4) NOT NULL default '0';
ALTER TABLE `piwik_report` ADD COLUMN `evolution_graph_within_period` TINYINT(4) NOT NULL DEFAULT 0;
ALTER TABLE `piwik_report` ADD COLUMN `evolution_graph_period_n` INT(11) NULL;

*** End of Dry Run ***

Mentioned in SAL (#wikimedia-operations) [2018-12-05T09:07:10Z] <elukey> matomo read only + upgrade to matomo 3.7.0 on matomo1001 - T209808

elukey added a subscriber: Nuria.Wed, Dec 5, 9:22 AM

Piwik/Matomo upgraded, but while testing the users I noticed that the piwik user outlined in https://wikitech.wikimedia.org/wiki/Analytics/Systems/Piwik#Access seems having a different password. @Nuria: I tried to change the pass and it seems that it needs more than 6 chars, so it must be another one. Shall we update wikitech?

elukey set the point value for this task to 5.Wed, Dec 5, 9:22 AM
elukey moved this task from Next Up to Done on the Analytics-Kanban board.
Nuria closed this task as Resolved.Mon, Dec 10, 5:58 PM