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
Table layout broken in hierarchy view #8506
Comments
Is it possible that you create an account with view access to your Piwik installation so we can debug? If so, please send us credentials to "hello at piwik.org" and comment here afterwards (just in case it goes to spam folder). You could delete the account directly after we had a look again |
We will discuss this. I will let you know if I know more. |
Mail sent from r*.k******@outlook.com. We also had error messages obviously caused my nginx pagespeed, but they does not seem to have anything to do with this issue. |
Any news here? Did you had a look into our installation? |
I just had a look and it seems to be caused by page-speed probably see eg #5081 (comment). Can you try to disable it? For more technical users: Something adds a Also possible that this is done by another extension. |
We will look into it again. |
Okay, so yes, it was Pagespeed. So we have disabled it and it worked. However we don't want to disable it for the whole site. We're using nginx with Plesk 12. |
I mean as we use nginx we tried it with |
Sorry we cannot give pagespeed support here. If someone knows the answer please comment here. Feel free to ask in the forum as well ( http://forum.piwik.org/ ) there might be some more users that can help you. Will close the issue as actual problem is resolved |
With Piwik 2.14.3 in Firefox 39 the tables seem to be a bit broken. Basically you can only see numbers, hyphens and a few URLs (I censored them below) - but all of them in one bunch.
But this only happens if I view the table (in the actions part) in the folded (hierarchy) view. If I view it in the unfolded view all looks right.
This is a 3D view of the table:
The text was updated successfully, but these errors were encountered: