bertram
(Bertram Croes)
June 14, 2023, 12:42pm
1
Hi, we are looking to upgrade from Matomo 3.1.1. on-premise hosted on our AWS Cloud account. Having gone through a lot of existing questions about this, I saw a lot of people encountering issues when doíng this. What is the recommended path to upgrade to the latest version? Would be best to upgrade to one ore more versions step by step before going straight to the latest from 3.1.1.? Would be great to get some advice on an approach that reduces the chances of downtime. Many thanks!
Hi @bertram
I would suggest you update:
To the latest 3.x version
Then to the 4.0 version
Then to the latest 4.x version
You may also check if you run the PHP supported versions (in the changelog, there is some PHP versions missings):
# Matomo Platform Changelog
This is the Developer Changelog for Matomo platform developers. All changes in our HTTP APIs, Plugins, Themes, SDKs, etc. are listed below.
The Product Changelog at **[matomo.org/changelog](https://matomo.org/changelog)** lets you see more details about any Matomo release, such as the list of new guides and FAQs, security fixes, and links to all closed issues.
## Matomo 5.0.0
### Breaking Changes
* AngularJS has been completely removed from the code base, existing AngularJS code will no longer work. It is recommended to convert that code to Vue.
* jQuery has been updated to 3.6.3. Please check your plugins javascript code if it needs to be adjusted. More details can be found in jQuery update guides: https://jquery.com/upgrade-guide/3.0/ and https://jquery.com/upgrade-guide/3.5/
* The `Common::fixLbrace()` function has been removed. It was only necessary for AngularJS and no longer needs to be used.
* The deprecated `JSON2` API format has now been removed. We recommend switching to the `JSON` renderer, which behaves the same.
* The javascript event `piwikPageChange`, which is triggered when a reporting page is loaded, has been renamed to `matomoPageChange`. Ensure to update your implementation if you rely on it.
* The deprecated javascript functions `broadcast.init`, `broadcast.propagateAjax` and `broadcast.pageLoad` have been removed.
* Plugin names are now limited to 60 characters. If you used to have a plugin with a longer name, you might need to rename it.
* The `instance_id` configuration does no longer support characters other than `a-z`, `0-9` and the special characters `.-_`. If the configured value contains other characters, they will be simply removed.
* When an invalid token is provided in an API request, a 401 response code is now returned instead of 200 response code.
* By default, the `file://` protocol is no longer tracked. To enable tracking of the `file://` protocol use the new JavaScript tracker method `enableFileTracking` ([learn more](https://matomo.org/faq/how-to/why-is-no-data-tracked-for-local-files/)).
This file has been truncated. show original
I think update to PHP 7.2.5 could be sufficient.
bertram
(Bertram Croes)
June 14, 2023, 2:59pm
3
Hi Philippe,
Many thanks for your quick response and recommendation. We will try this and update this thread with how it went so others can benefit as well. Will be in touch.
1 Like