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

Jump to bottom

Unexpected website error when using idSite=all #12312

Closed

gricey432 opened this issue Nov 30, 2017 · 5 comments

Contributor

gricey432 commented Nov 30, 2017 •

edited

Using the API

https://example.com/?module=API&method=Live.getLastVisitsDetails&idSite=all&period=day&date=today&format=json&token_auth=xxx

Should return the latest visit details for all sites on the server, instead I get

{
result: "error",
message: "An unexpected website was found in the request: website id was set to '0' ."
}

The text was updated successfully, but these errors were encountered:

gricey432 changed the title ~~Unexpected website when using idSite=all~~ Unexpected website error when using idSite=all

Contributor Author

gricey432 commented Nov 30, 2017

Additionally if I use idSite=1,2,3 I only get the data for idSite=1. I have a feeling this issue is only on the Live endpoint though, not sure..

Contributor

tassoman commented Dec 1, 2017

I bet idSite must be a single integer. You're asking the getLastVisitsDetails method in the Live plugin. If you want all sites results, you must query Multisite plugin.

There's an example on demo site

Contributor Author

gricey432 commented Dec 5, 2017

So this is expected behaviour?

The Standard API parameters section of the docs says all and 1,4,5,6 are valid values, and the Live! section doesn't mention otherwise.

Findus23 mentioned this issue

GDPR tool doesn't work when selecting all websites #12842

Closed

Member

Findus23 commented Jun 27, 2018

@gricey432 Did you test this in the latest version?

I think #12854 should have solved this issue.

Contributor Author

gricey432 commented Jun 27, 2018

Just tested and this appears to be fixed!

Resolved in #12854

gricey432 closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment