What’s your screen resolution?
Thread Starter
yk11
(@yk11)
It happens in any resolution. My monitor is 1920×1200, and the widgets are cutoff no matter how I size the browser. This happens in both Firefox and Chrome.
See screenshot
It looks like a conflict with another plugin you are using. For some reason, this other plugin is changing the line height (or the padding?) of P tags, which we use for the report rows. Can you try deactivating all your other plugins, to see if the problem disappears?
Thread Starter
yk11
(@yk11)
I looked into it, and the p tags are not overridden (the rules are coming from slimstat.css for line-height, font-size, margin, etc.).
This would also not affect the chart, which does not use p tags (only div).
See screenshot (font-size of 12px is my manual change in Chrome to see if it affects thing, which it did not)
Any other CSS rules being overridden at any level? (divs? spans?)
Thread Starter
yk11
(@yk11)
Not that I can see (I added screenshot to previous post). I actually wish that I could override css in the admin pages, but I don’t think you can. (I use Custom CSS for the main site to tweak things)
The Custom CSS field in the settings allows you to override any CSS rule 😉
Thread Starter
yk11
(@yk11)
Ah, nice feature :). How would I add the following:
.postbox .wide .chart, .postbox .normal { height 295px; }
.slimScrollDiv { height: 260px; }
The link to the FAQ points to the support pages, which do not have an entry on this.
Thread Starter
yk11
(@yk11)
Thanks! I got it to work. FYI, I had to add “!important” to the css or it got overridden by the the slimstat.css rules.
That’s strange, because the inline CSS is enqueued AFTER slimstat.css. Anyway, I’m glad it works. A vote for Slimstat would be a nice way to say thank you!
Thread Starter
yk11
(@yk11)
I wanted to thank you for your help.
I couldn’t let it go, so I installed your plugin on another site I have and there it worked fine. It allowed me to trace the issue to a theme specific css bit that is used for the admin panel (hence affecting your plugin too).
I corrected their code (poor code is everywhere, even in paid for themes) and now all is well.
My vote is in!
Great, thanks for the update!
