Support » Plugin: The Events Calendar » [Plugin: The Events Calendar] Bad Font Sizes

  • Hey TEC team,

    I like 16px as a font size, and frequently use it, but I don’t understand why you’re putting that into the plugin’s styles for things that the theme really should control.

    For instance, line 356 in events.css:

    .events-archive .tribe-events-event-entry p, .venue-events .tribe-events-event-entry p {
    	font-size: 16px;
    	line-height: 24px;

    All three of those rules override styles I _always_ set in my stylesheets, and it’s a pain to have to override those.

    I completely understand the need to provide _some_ styles to make the plugin look good out of the box, but that strikes me as going too far.


    p.s I know I owe you a response to a different thread, still. My apologies. It’s coming.

Viewing 11 replies - 1 through 11 (of 11 total)
  • Plugin Author Rob La Gatta


    This raises a good question, mrwweb – I appreciate you pointing it out. My guess is that this relates to the overall goal of making it integrate cleanly out of the box, but I’m wondering if based on your note we’ve taken it too far.

    That’s a tad outside my area of expertise, but I’ve asked one of the primary devs on this plugin to take a look and respond directly. Thanks again for the heads up…stay tuned and we should have you a response shortly.

    Plugin Author Rob La Gatta


    Hey again mrwweb. I spoke to our devs about this today, and it looks like they’re generally on your same page. Since it looks like you know how to fix it yourself it sounds like you’ve got a temporary solution for now. In the longer term, we are workin on a skeleton stylesheet that removes all uneeded font-size, color, etc in an attempt to hopefully be more seamless with other themes, and the idea will be that the user can select the full stylesheet or the skeleton one. We’ve got the first version done and just need to test it a bit more before deploying. Realistically this should be included in 2.1, which will be out by the end of the year.

    The good news is that, since you clearly know what you’re doing, it should be a real quick tweak (20 seconds or so) to modify this as you want in the interim.

    Hope that helps. If not, let me know and I can follow-up. Otherwise let me know if you think we can mark this RESOLVED. Cheers!

    Thanks for the reply, Rob. I’ll go ahead and mark it resolved.

    It’s certainly not a problem that can’t be resolved by the user, but it is extra code that has to be overridden with even more extra code. That’s just suboptimal and probably not a great experience for a lot of people.

    I’m glad to hear that you’re changing directions with the theming stuff. I think that sounds like a good solution.

    On that note, please don’t use !important

    .eventsListWidget li, li.hentry, .eventsAdvancedListWidget li, li.hentry {
    margin:6px 0 !important;
    padding: 0 0 10px 0 !important;

    I need to override these and now I have to disable the entire events.css stylesheet to do it.

    Plugin Author Rob La Gatta


    Thanks, mrwweb!

    tim_ward…this is a solid suggestion, and you’re not the first to make it. We’ve actually got those !important references stripped out in the 3.0 code we’re currently working on, based on a past request for this. So know that relief is coming in that regard as well.

    @tim_ward, if you use a higher CSS specificity combined with !important, your styles “win” (though it’s a Pyrrhic victory). Alternately, enqueue your styles to load after the TEC ones and you can even use the same selector. I think the $handle you’d want to list as the dependency is 'tribe-events-calendar-style', though I didn’t look that hard.

    roblagatta: Good to hear. I actually later discovered you could simply overwrite the events.css (handy little feature that) in your own template, which made it less of a pain than I at first thought.

    mrwweb: I’m aware of the ways around it, it’s just that where I work using !important in our own style sheets is… frowned upon. And for good reason.

    @tim_ward. I didn’t realize the events.css could get overwritten. Good tip.

    And yes, !important is the spawn of Satan. You just sometimes find yourself at the crossroads.

    Plugin Author Rob La Gatta


    Death to !important…at least in the context of The Events Calendar.

    Thanks for the bit of knowledge on the CSS file too, Tim. Appreciate the heads up and I know other users will too.

    So how do you overwrite events.css? I’m just trying to get the font styles and colors to match up with my theme and so far no luck.

    Plugin Author Rob La Gatta


    Hey morganictrie. You can overrwrite events.css by following the template override procedure documented at

    Hope that helps. If it doesn’t, we can definitely try to help…but please open it as a new thread rather than commenting into this closed one, if you’d be so kind. Thanks!

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘[Plugin: The Events Calendar] Bad Font Sizes’ is closed to new replies.