[Steve]

Thanks George. Yeah, that’s the right idea using categories and then targeting those classes. I was looking for a way to not make any extra categories in order to keep the category list simple.

I think the solution for now is to use tags and then hide them from the single event display. In future it might be cool to provide the ability to add custom css classes or a ‘Featured Event’ checkbox that could add a new class. Cheers!

[Steve]

Yes, that must have been it. For future releases/users it would be useful to have this be more intuitive. One possible way to do this would be to not display the ‘Save Changes’ button until the license is validated, or allow the license to save, then validate. Thanks for your help.

[Steve]

looks like it worked! would love to know more about why that class doesn’t repeat, though I expect that’s something to take up with the developers. Thanks.

[Steve]

I’m not running any caching plugins FWIW.

[Steve]

Thanks!

[Steve]

Here’s the specific rule:

.tribe-events-calendar .tribe_events:not(.tribe-recurring-event) {
background: #f4d575 none repeat scroll 0 0;
}

• This reply was modified 10 years, 2 months ago by Steve.

[Author]

Posts