Hi @mackieee
Thanks for the report. It definitely looks like a bug we need to address.

1. Can you reproduce this issue on the https://demo.piwik.org ?
2. could you send us via http://piwik.org/contact/ your PIwik URL and temporary Username/pasword so we can see this issue?

1. It's not re-producible on the Demo-site. I can see that it does continue breakdown to the next level via another collapsible tooltip.

2. Sent Email! :)

@sgiehl Would be great if you could take a look at this one

Issue was caused by mod_pagespeed .

@mattab We should maybe add a FAQ item that Piwik might not work correctly if mod_pagespeed is activated or even add a system check for that. thoughts?

@sgiehl
we already have this system check https://github.com/piwik/piwik/blob/3.x-dev/plugins/Diagnostics/Diagnostic/PageSpeedCheck.php#L25-24

Is this diagnostic correctly triggering a warning?

The system check does warn of the PageSpeed module being enabled, which I admittedly didn't check. So user error :)

I would suggest on expanding on the various(?) front-end issues that mod_pagespeed has on the Admin pages of Piwik. Anything to add for future google searches! But understandably it doesn't sound like this has happended very often so I open this ticket will be suffice.

Thanks to you both for your awesome support & product :)

MackieeE

Good idea, we'll improve the label and make it more clear what problems it causes.

Btw, did you notice any other problems besides that one reported here?

from email:

However, with the help of the query string tests that ModPageSpeed offer:

https://modpagespeed.com/doc/experiment#ModPagespeed

By appending &PageSpeed=off to the URL, it worked perfectly with Page-speed disabled:

So maybe one solution could also be to automatically append this parameter to index.php requests, when we detect mod_pagespeed is enabled?

Morning! That would be a good last resort solution. I think your docs do rightly suggest turning it off at the .htaccess level. Which strangely I was unable to set on the shared host.

I have noticed one more action, however I'm not sure it's PageSpeed related, as even turning it off via the Query string has no effect (Maybe because it's a seperate web request). See below for example:

When clicking the "Open Row Evolution" under Browsers, for Chrome specifically:

The resulting modal spills out:

,

Yes, that seems to be mod page_speed as well. We should keep on suggesting to turn it off.

@mattab Should anything be done here?

@sgiehl Yes let's just add a message that makes the failed system check more prominent. For example "[...] cause several issues in Piwik such as: broken Pages reports, broken Row Evolution, and other issues hard to troubleshoot. Please disable mod_pagespeed on this server."