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
Charts - charts cropped at bottom (PHP 5.1.x) #2504
Comments
Attachment: Plots cut off at the bottom |
Hi! I can verify that for our Piwik Installation: [50%)]([Image(Piwik_plots-cut-off.png,)] We use a CentOS 5.5 Installation with a custom PHP 5.1.6 build but we cannot update the PHP version. We'd be happy to help finding what's the cause. greetings, Daniel |
5.1.6 is from Aug 2006, ie. 5 year old. Not going to fix this issue on such old version since issue is not critical |
Are we finally raising requirements? |
Well, this is a "critical" bug for all user who are forced to use some old PHP as the charts are crap to use and how should someone supposed to use the core functionality (analytics) of piwik if he can't read the graphs? |
+1 for raising requirements; I understand the frustration if somebody is stuck up with an old PHP version, but we'll end up with tons of complex legacy-code if we workaround everything. |
I took a quick look at the jqplot code, and it looks like a .js bug (i.e., not php 5.1.x specific). Can you guys test this patch? In libs/jqplot/jqplot.lineRenderer.js, change this:
to:
|
Replying to vipsoft:
|
Did you delete the files in tmp/assets/* and clear your browser cache? |
OMG [4964] fixed this one too? |
Confirmed! Works now. @vipsoft: Thank you very much! I really appreciate fixing this bug! You saved me from several days of work. |
We got a report in the german forum that there were issues with the new jplot charts when php 5.1 was used (see topic "[gelst] Besucher-Graph nach update auf 1.5"). The charts were cut off in the bottom and the div which holds the canvas (class="jqplot-axis jqplot-yaxis" ) has only 2 canvas elements instead of 3 in the regular view.
Upgrading to php 5.2 fixed that for at least one user.
The text was updated successfully, but these errors were encountered: