Skip to content


Actions -> Pages hangs (Loading...) #1420

anonymous-piwik-user opened this Issue · 6 comments

3 participants


I'm using Piwik on a large web site with up to 400.000 actions per day.

The Actions -> Pages view stopped working, I think it happened updating to Piwik 0.6.2. It seems that I'm not the only one - there is a thread in the Piwik forum:

The Online Demo on your site seems to have the same problem. If I for example go to Actions -> Pages -> trac -> ticket the "Loading..." sign comes up and that's all.

Piwik Open Source Analytics member

While I couldn't verify earlier, I agree that even the demo is failing when trying to open trac / ticket / *

The http request returns nothing instead of returning the HTML (or an error):

I'm not sure what the error is as even the apache error logs are empty.

Can you check your http requests with firebug and see if you get some HTML back?

Do you have errors in your error logs?

Piwik Open Source Analytics member

Regarding the demo, trac/ticket seems to be the only directory not loading. Other directories load fine for me. Do you see the same thing in your Piwik install, or are most directories not loading?

Piwik Open Source Analytics member

(In [2292]) Fixes #1420 Shame on me... I left a smarty {debug} statement in there. Interestingly, this was making the whole http request fail (return a blank http 200 response) in some still unidentified cases..

Piwik Open Source Analytics member

(In [2293]) Refs #1420 Adding unit tests to check that there is no {debug} statements left in code


Wow, you are fast! Thank you very much for your quick reaction and the fix. Works like a charm now.


Shame on me, too. I saw that debug in the original changeset and assumed it was a work in progress, and never went back to see if you had later taken it out.

@anonymous-piwik-user anonymous-piwik-user added this to the Piwik 0.6.3 milestone
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.