matomo-for-wordpress
matomo-for-wordpress copied to clipboard
matomo-org
Matomo 4.12.2
https://innocraft.atlassian.net/browse/WBS-521 fixes #650
Description:
Please include a description of this change and which issue it fixes. If no issue exists yet please include context and what problem it solves.
Review
- [ ] Functional review done
- [ ] Potential edge cases thought about (behavior of the code with strange input, with strange internal state or possible interactions with other Matomo subsystems)
- [ ] Usability review done (is anything maybe unclear or think about anything that would cause people to reach out to support)
- [ ] Security review done
- [ ] Wording review done
- [ ] Code review done
- [ ] Tests were added if useful/possible
- [ ] Reviewed for breaking changes
- [ ] Developer changelog updated if needed
- [ ] Documentation added if needed
- [ ] Existing documentation updated if needed
Hi @lance-matomo, as discussed in the JIRA issue, I've applied the content of both:
- https://github.com/matomo-org/matomo-for-wordpress/wiki/Updating-Matomo-core-to-a-newer-version-within-Matomo-for-WordPress
- https://github.com/matomo-org/matomo-for-wordpress/wiki/Create-new-release
@mattmary it would be wise as we have a significant Tag Manager regression in 4.12.2.
HI @justinvelluppillai , I understood it has been fixed in the .2. This is in the .3 instead ?
@mattmary yes that's correct, a problem still exists in .2 - 4.12.3 is aiming to be out by lunch time NZT today
Hello @lance-matomo
I've upgraded to 4.12.3 and reapply the steps described in
- https://github.com/matomo-org/matomo-for-wordpress/wiki/Updating-Matomo-core-to-a-newer-version-within-Matomo-for-WordPress
- https://github.com/matomo-org/matomo-for-wordpress/wiki/Create-new-release