-
Notifications
You must be signed in to change notification settings - Fork 59
Improvements to MTM tracker to allow full _paq functionality #594
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
@AltamashShaikh Any ideas what is causing the JavaScript build to fail? It appears to have started with the previous commit, but I'm not seeing what in that commit would cause the failure. |
Seeing the same issue in FormAnalytics build and trying to figure out, @sgiehl do you have any idea why this is breaking ? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@AltamashShaikh I didn't think that any specific changes were necessary to make |
…:matomo-org/tag-manager into pg-1718-fixing-tag-manager-tracker-issue
Template/Tag/MatomoTag.web.js
Outdated
@@ -117,39 +128,167 @@ | |||
} | |||
configuredTrackers[variableName] = tracker; | |||
|
|||
var requireCookieConsentIndex = disableBrowserFeatureDetectionIndex |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also can we document this, whenever any new config is supported we should not forget to add new variable here and support it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure. Do you think it would be best to note it in the developer documentation, the FAQ, or both? Any specific page recommendations?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Developer documentation should be fine
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@snake14 Left few suggestion for comments and doc and was able to test with the resources you shared and looks good to me
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Except for adding the documentation all looks good 👍
Thank you @AltamashShaikh . I went ahead and created a documentation PR, so I'm going to merge this PR. |
@snake14 @AltamashShaikh It doesn't look like a useful move to simply merge a PR that is known to break the tests. |
@sgiehl We weren't sure since the errors were identical to the JavaScript build errors in other plugin branches. Plus, the changes have been tested by Altamash, Thomas, and myself without issue. Is the issue in the code or is the build too brittle? I can try a slightly different approach around Edit: I created a new PR and tried a few changes to make sure that I wasn't reassigning |
@sgiehl Thanks for pointing it out and we will be careful next time, actually I did test this on local and it seems to passing so we thought it as a recent random JS tests failing on github-actions and proceeded ahead |
@AltamashShaikh If you think something fails randomly simply try to rerun the job a couple of times and see if its really random or fails always... |
Description:
This is to remedy the fact that _paq.push doesn't work reliably while using MTM.
Review