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
visitIp not included in Live.getLastVisitsDetails since 1.13.1 #15421
Comments
visitIp
not included in Live.getLastVisitsDetails
since 1.13.1
That hasn't been changed. The visitIp should still be included. |
@Romain are you using a valid token_auth of a user with at least view access when fetching the list of segments? There was some refactoring which was needed for some issue but it should still behave the same. I was going to say you could workaround by adding a cc @diosmosis |
Actually, I was reading this wrong. This is not about segments. |
This works for me. It looks like the token_auth is not valid very likely. Maybe the token was regenerated? |
Hi @tsteur , Thanks for having a look a this. Here is what I'm doing:
I tried to pass the |
I also tried |
@Romain I see. Thought you do this through the HTTP API. I just tried to reproduce this and it seems to work for me. Maybe you have some other plugins active that maybe change this behaviour? |
@tsteur Unfortunately I don't. On my dev setup, I just have Matomo, my plugin, the LogViewer and the VisitorGenerator. On my prod setup, I just have Matomo and my plugin. Here are the plugins that are installed on my dev setup: |
Just to give you more information on the data I get. Here is a sample of code more detailed:
This logs what follows:
|
Ok, I solved it by changing my request this way:
Thank for your help. |
I updated Matomo from 1.13.0 to 1.13.1 last week.
Since then, my plugin displays incoherent data.
Digging into this problem, I realized that this new version of Matomo introduced a change in the content returned by the API endpoint
Live.getLastVisitsDetails
. ThevisitIp
key is not included in the JSON response anymore.Could you include this value again in the response?
Thanks!
How to reproduce
The text was updated successfully, but these errors were encountered: