Added new event, which is triggered after the invitation to a user has been resent.
Added new event, which is triggered after a new user has been invited.
If the Matomo instance can't make requests to via HTTPS this can be set to 1 to force matomo marketplace and matomo api requests to use HTTP instead of HTTPS.
A general config setting force_matomo_http_request defaulting to 0.
Directly creating a new user is still possible using the API. Instead an invitation can be sent via email.
The user management UI no longer allows direct creation of a new user (with a password).
This can for example be used if you need to forward your users to an external service like SSO or payment and don't want any visits or conversions being attributed to those services. If a referrer matches an entry on that list, it will not be passed with the tracking requests and the attribution cookie will stay unchanged. They allow setting and receiving the referrers the JavaScript tracker should ignore.
The methods setExcludedReferrers and getExcludedReferrers have been added to the JavaScript tracker.
Existing iframe opt-outs will still work, but iframe opt-out code will no longer be generated by the UI as support for third party cookies in iframes is being discontinued by most major browsers.
The privacy manager iframe opt-out UI has been replaced with a choice of either generating JavaScript opt-out code which uses the Matomo tracker, or generating self-contained JavaScript opt-out code which directly sets the consent cookies.
When removing a site through the leteSite API using a session authentication, a new parameter passwordConfirmation needs to be sent along with the request containing the current password of the user issuing the API request.
Added new event erRequiresPasswordConfirmation, which can be used in login plugins to circumvent the password confirmation in UI and for certain API methods.
When inviting a user through the UsersManager.inviteUser API using a session authentication, a new parameter passwordConfirmation needs to be sent along with the request containing the current password of the user issuing the API request.
When adding a user through the UsersManager.addUser API using a session authentication, a new parameter passwordConfirmation needs to be sent along with the request containing the current password of the user issuing the API request.
When removing a user through the leteUser API using a session authentication, a new parameter passwordConfirmation needs to be sent along with the request containing the current password of the user issuing the API request.
The Product Changelog at /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. All changes in our HTTP API's, Plugins, Themes, SDKs, etc. This is the Developer Changelog for Matomo platform developers.
0 kommentar(er)
