I’m not sure entirely what you mean; each post is rendered inside it’s own div with a class ‘f2-tumblr-post’ which has a 16px margin on the bottom.
You could certainly tweak the styling in your theme – if you need a full breakdown of all the styles let me know and I can write it up – but by default I’m surprised you’re seeing “no spacing” at all. If you have an example URL or screenshot to show the problem, that would be super helpful!
Thanks for getting back to me so quickly.
Here is the URL: http://jchriscookphotography.com/project-365/
It seemed weird to me as well. I poked around and noticed that f2-tumblr-widget/css/widget.css is inactive. Does that have something to do with it?
I’m not sure entirely what you mean by “inactive”?
There’s something very wierd going on for sure; the stylesheet is visible, but for some reason isn’t getting applied – I can only assume that there is something odd in your theme or other plugins that is somehow blocking the stylesheet (although I can’t think off the top of my head what that might be).
Is the theme you’re using public? If I can replicate it on my dev system, I might have more luck working out what’s going on…
I go in to edit the widget.css file and at the top of the screen it says: “Editing f2-tumblr-widget/css/widget.css (inactive)”
I agree it’s very strange. I think it is something in my theme and am sending this discussion thread to my developer.
The theme is LesPaul, available on ThemeForest.
Hopefully, we can collaborate and figure this out. Thanks again for your responsiveness. A five star rating awaits if we get this nailed down!
Ahh; I think that’s a bug in the WordPress file editor – it tends to say “inactive” about certain files within a plugin, even when it’s active.
I’ll be interested to see what your theme developer makes of it; I can only guess that something in the theme styles is managing to over-ride the plugin stylesheet somehow.
Ok, done some more digging and it’s definitely my fault and not your theme!
If you want the gory details – I’d used the wrong style of comment in the stylesheet (which is totally valid in lots of other languages, but not CSS…) which seems to have the effect of silently disabling the next style entry. Because it only affected a couple of entries, which are often over-ridden either within the widget itself or in the theme, I’d never spotted it in testing.
Many apologies for that; I’ve just pushed a fix out (v0.2.5) which should be available for download Real Soon Now.
I appreciate that! And you got some serious props from my developer. We both respect your honesty and responsiveness!
We’ve made a couple of changes to our CSS until the update arrives.
Be well!
I’m flagging this as resolved; obviously let me know if you’re still having issues and I’ll unresolve it 🙂
