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
TypeError: Converting circular structure to JSON in Angluar apps in Preview Mode #487
Comments
User downgraded to 4.9 and the same issue is still present. |
@Starker3 I tried replicating the issue by creating a test HTML, but unable to reproduce it
|
@AltamashShaikh I'll ask the user if they have any public facing sites that we can try test this on. |
He everyone this is a regression and I was able to identify the cause, will raise a PR for same to fix it |
@AltamashShaikh hi friend. Is Bug have been comleted? I dont see changing( О Matomo 4.10.1, http://joxi.ru/nAyw9pbH9z94ym , http://joxi.ru/J2bG3xDTq6qlBA |
Hey @AltamashShaikh. We installed Matomo 4/11, but preview whatever with error. What i do wrong? |
@mattoii Can you check if the following file(plugins/TagManager/vue/src/Debugging/Debugging.vue) has identical content on your instance? |
@AltamashShaikh yes, what else can i check? |
@mattoii is there any way I can test it? |
@mattoii The fix is with |
@AltamashShaikh we already installed last version TM and we created new tag and installed it. We need to waiting new version TM or i do wrong? |
@mattoii you have upgraded to
|
@AltamashShaikh hi, we updated it through web interface Is this enough or should I do something else? |
Hey @mattoii |
Same type of issue as #185
However, this is happening on the most recent version of Matomo (4.10.0).
This issue seems to only be happening on sites that use Angular (PHP sites for example do not have the issue using the same container).
The user was able to reproduce the error by first clicking a button on their site and then clicking on the Event in the preview mode iFrame:
This results in a blank preview page and the above error in the console:
I've asked the user to confirm if the same was happening in 4.9 or if it only started after the update to 4.10.0
Will add a comment here if I get confirmation about that.
The text was updated successfully, but these errors were encountered: