You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Can you reproduce this problem on the demo.piwik.org ?
Also maybe your bug is similar to an existing report see for example #4815 or #3609 or #4595 - please post in the related ticket if possible (with steps to reproduce the issue)
i would assume all you need to reproduce this on demo.piwik.org is to have a url that has escaped spaces '%20', but i don't see any page urls with such a condition
mattab
changed the title
escaping issue in newest piwik version
Transitions show no data when page contains %20
Oct 28, 2014
while trying to fetch transitions on the newest piwik version (2.8.3) i get
There's no data for http://base url/Gene Full Report Records
Either the action had no pageviews during the period
or it is invalid.
Go back to the previous action
when i click on a transition report in either the pages, or entry pages widget.
looking into it a bit more, the request:
http://piwik_url/index.php?date=2014-10-26&actionType=url&actionName=http%3A%2F%2Fbase_url%2FGene+Full+Report+Records&expanded=1&format=JSON&module=API&method=Transitions.getTransitionsForAction&idSite=1&period=day
results in
{"result":"error","message":"NoDataForAction"}
/////
it seems that there is an escaping issue here. if i naively escape my url (just needs spaces) here:
plugins/Transitions/API.php
then deriveIdAction succeeds (although the fetch still fails in addInternalReferrers farther down the road, i haven't continued to look into it.)
here is what the url looks like in mysql:
mysql> SELECT idaction, type, name FROM piwik_log_action limit 100
-> ;
+----------+------+-----------------------------------------------------------------------------------+
| idaction | type | name |
+----------+------+-----------------------------------------------------------------------------------+
...
| 3 | 1 | base_url/Gene%20Full%20Report%20Records
The text was updated successfully, but these errors were encountered: