-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
PHP Arrays not Serialized by Default #6137
Comments
I'm getting the same format from
|
... the root cause is that the new Php Renderer module does not serialize Arrays by default: https://github.com/piwik/piwik/blob/master/plugins/API/Renderer/Php.php#L50 |
@claytondaley thanks for the report! Do you think it's a regression and that it used to return serialized data in an older Piwik version? |
I honestly can't say. For sure the previous version returned serialized data by default and the contributor who refactored this code made the same change in another part of the new file. @tsteur did the refactor and might know off hand. |
This seems to fix the issue with WP-Piwik however it causes errors on my Visitor Map section inside Piwik (see below). Could this be a problem with the visitor map?
|
As noted in the patch, I have fixed UserCountryMap. I also cited the section of the documentation that leads me to believe that the patch (and not the current state) produces the expected behavior. |
This is definitely a regression, and has the nasty side-effect of compelling WP-Piwik to create spurious new site records. |
Thanks for the report. I've added some test for this particular case so it should not regress again. feel free to report any other issue, we can fix them until 2.7.0 release due next week. |
Calls to SitesManager.getSitesIdFromSiteUrl&format=PHP&... are returning data structured like
instead of serialized data (e.g. SitesManager.getJavascriptTag&format=PHP&...):
This was discovered while "debugging" an issue in WP-Piwik but I confirmed the root cause was Piwik by pasting API calls directly into the browser. I assume this is an unintended change since the new response cannot be unserialized by PHP code.
The text was updated successfully, but these errors were encountered: