Matomo database will be upgraded from version 3.3.0 to the new version 3.8.1.
The following dimensions will be updated: log_visit.location_region.
Important notes for large Matomo installations If you have a large Matomo database, updates might take too long to run in the browser. In this situation, you can execute the updates from your command line:
php /homepages/7/d356555543/htdocs/mamoto/console core:update
If you manage a high traffic Matomo server, we recommend to momentarily disable visitor Tracking and put the Matomo User Interface in maintenance mode .
›Click here to view and copy the list of SQL queries that will get executed
#FYI: these are the SQL queries that will be executed to upgrade your database to Matomo 3.8.1 CREATE TABLE `matomo_fh_privacy_logdata_anonymizations` (`idlogdata_anonymization` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT, `idsites` TEXT NULL DEFAULT NULL, `date_start` DATETIME NOT NULL, `date_end` DATETIME NOT NULL, `anonymize_ip` TINYINT(1) UNSIGNED NOT NULL DEFAULT 0, `anonymize_location` TINYINT(1) UNSIGNED NOT NULL DEFAULT 0, `anonymize_userid` TINYINT(1) UNSIGNED NOT NULL DEFAULT 0, `unset_visit_columns` TEXT NOT NULL DEFAULT '', `unset_link_visit_action_columns` TEXT NOT NULL DEFAULT '', `output` MEDIUMTEXT NULL DEFAULT NULL, `scheduled_date` DATETIME NULL, `job_start_date` DATETIME NULL, `job_finish_date` DATETIME NULL, `requester` VARCHAR(100) NOT NULL DEFAULT '', PRIMARY KEY ( `idlogdata_anonymization` )) ENGINE=InnoDB DEFAULT CHARSET=utf8; ALTER TABLE `matomo_fh_privacy_logdata_anonymizations` ADD INDEX index_job_start_date (`job_start_date`); ALTER TABLE `matomo_fh_plugin_setting` ADD COLUMN `json_encoded` TINYINT UNSIGNED NOT NULL DEFAULT 0; ALTER TABLE `matomo_fh_site_setting` ADD COLUMN `json_encoded` TINYINT UNSIGNED NOT NULL DEFAULT 0; ALTER TABLE `matomo_fh_site_setting` CHANGE `idsite` `idsite` INTEGER(10) UNSIGNED NOT NULL; ALTER TABLE `matomo_fh_plugin_setting` ADD COLUMN `idplugin_setting` BIGINT UNSIGNED NOT NULL PRIMARY KEY AUTO_INCREMENT; ALTER TABLE `matomo_fh_site_setting` ADD COLUMN `idsite_setting` BIGINT UNSIGNED NOT NULL PRIMARY KEY AUTO_INCREMENT; ALTER TABLE `matomo_fh_log_profiling` ADD COLUMN `idprofiling` BIGINT UNSIGNED NOT NULL PRIMARY KEY AUTO_INCREMENT; ALTER TABLE `matomo_fh_access` CHANGE `access` `access` VARCHAR(50) NULL; ALTER TABLE `matomo_fh_access` DROP PRIMARY KEY; ALTER TABLE `matomo_fh_access` ADD COLUMN `idaccess` INT UNSIGNED NOT NULL PRIMARY KEY AUTO_INCREMENT; ALTER TABLE `matomo_fh_access` ADD INDEX index_loginidsite (`login`, `idsite`); ALTER TABLE `matomo_fh_user` ADD COLUMN `ts_password_modified` TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP; CREATE TABLE `matomo_fh_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 `matomo_fh_report_subscriptions` ADD UNIQUE KEY unique_token (`token`); ALTER TABLE `matomo_fh_user` CHANGE `ts_password_modified` `ts_password_modified` TIMESTAMP NULL; UPDATE `matomo_fh_user` SET ts_password_modified = NULL; ALTER TABLE `matomo_fh_site` ADD COLUMN `creator_login` VARCHAR(100) NULL; ALTER TABLE `matomo_fh_goal` ADD COLUMN `event_value_as_revenue` tinyint(4) NOT NULL default '0'; ALTER TABLE `matomo_fh_report` ADD COLUMN `evolution_graph_within_period` TINYINT(4) NOT NULL DEFAULT 0; ALTER TABLE `matomo_fh_report` ADD COLUMN `evolution_graph_period_n` INT(11) NULL; ALTER TABLE `matomo_fh_user` ADD COLUMN `twofactor_secret` VARCHAR(40) NOT NULL DEFAULT ''; CREATE TABLE `matomo_fh_twofactor_recovery_code` (`idrecoverycode` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT, `login` VARCHAR(100) NOT NULL, `recovery_code` VARCHAR(40) NOT NULL, PRIMARY KEY ( `idrecoverycode` )) ENGINE=InnoDB DEFAULT CHARSET=utf8; CREATE TABLE `matomo_fh_tracking_failure` (`idsite` BIGINT(20) UNSIGNED NOT NULL, `idfailure` SMALLINT UNSIGNED NOT NULL, `date_first_occurred` DATETIME NOT NULL, `request_url` MEDIUMTEXT NOT NULL, PRIMARY KEY ( `idsite`, `idfailure` )) ENGINE=InnoDB DEFAULT CHARSET=utf8; CREATE TABLE `matomo_fh_brute_force_log` (`id_brute_force_log` bigint(11) NOT NULL AUTO_INCREMENT, `ip_address` VARCHAR(60) DEFAULT NULL, `attempted_at` datetime NOT NULL, PRIMARY KEY ( `id_brute_force_log` )) ENGINE=InnoDB DEFAULT CHARSET=utf8; ALTER TABLE `matomo_fh_brute_force_log` ADD INDEX index_ip_address (`ip_address`); ALTER TABLE `matomo_fh_log_visit` MODIFY COLUMN `location_region` char(3) DEFAULT NULL; ALTER TABLE `matomo_fh_log_conversion` MODIFY COLUMN `location_region` char(3) DEFAULT NULL;
Need help upgrading Matomo?
If you need support to upgrade your Matomo, the creators of Matomo are here to help you make the Matomo upgrade a success and provide all instructions, best practises and ongoing support. Contact the Matomo experts to get started upgrading your Matomo safely.
Ready to go?
The database upgrade process may take a while, so please be patient.
File integrity check failed and reported some errors. You should fix this issue and then refresh this page until it shows no error. Details
File integrity check failed and reported some errors. You should fix this issue and then refresh this page until it shows no error.
Files were found in your Matomo but we didn't expect them. --> Please delete these files to prevent errors. <-- File to delete: misc/internal-docs/content-tracking.md File to delete: misc/others/api_internal_call.php To delete all these files at once, you can run this command: rm "/homepages/7/d356555543/htdocs/mamoto/misc/internal-docs/content-tracking.md" "/homepages/7/d356555543/htdocs/mamoto/misc/others/api_internal_call.php"