[Barry]

Sure – a large portion of the team is based in the United States and so are enjoying some relaxation as I believe this is a public holiday there, so there may be some delays – we did post a notice to that effect:

Please note: Because it’s a holiday weekend in America, support will be lighter than usual from July 4 through July 7. We will be active on the forum during this time, addressing existing issues, helping users with 3.0 upgrade problems, etc. But we cannot guarantee our usual 24-hour response window. Support will resume in full and normal capacity on Monday, July 8. Happy Independence Day!

And we’re still providing coverage, so hang tight and we’ll get there as soon as we can.

[Barry]

That’s disappointing – you certainly shouldn’t have to do that. I’ve been working with a few different themes this morning and generally it appears as expected.

Are you in a position to switch to Twenty Twelve as a means of determining if the problem is with your theme or not (for instance, it may have some means of disabling featured images – or only enabling them – for certain post types) or else it could be a conflict with another plugin.

We’d really need to zero in on what’s causing it not to appear to get to the bottom of this one.

[Barry]

Hi Heather,

Looks like some CSS rules from your theme are leaking through and causing this.

As a starting point, please simply edit your theme’s stylesheet and add the following rule to the bottom of that file:

#tribe-events {
color: #000;
}

(If you prefer you can probably do this by setting up a new stylesheet for events – but please see the updated themer’s guide as this process has changed since 2.0.11 and you would need to rename events.css to tribe-events.css in addition to renaming the events directory tribe-events).

I hope the above gets you started, let me know if there is anything else or if that doesn’t help.

[Barry]

Hi Charlie – fantastic, thanks for figuring that out – I do believe that is the proverbial missing jigsaw piece. Now we’ve determined that, please bear with us while we see what we can do here.

[Barry]

It’s just the same as with regular WordPress posts (normally there is a “Featured Image” meta box within the post editor, or in this case the event editor, typically within the right hand column).

Do note that your theme must support featured images for this metabox to appear within the editor. These days most themes do support featured images, but if yours does not it is normally fairly easy to add support (though it would be best to reach out to the theme developer in case they have any best practices for this relating to their own theme).

[Barry]

Hi Chris,

Here are two good resources to get a feel for where templates are (and how they work) in the current release:

* Themer’s Guide at https://theeventscalendar.com/support/documentation/events-calendar-themers-guide/
* A video overview by our developer Jessica https://theeventscalendar.com/the-events-calendar-3-0-preview-talking-templates-with-jessica/

So there are actually a number of different approaches you might take, perhaps the simplest though is to add a short piece of code to your theme’s functions.php file, a bit like this:

http://pastebin.com/0Jmwju46

You would of course need to tweak it so it catches whichever custom fields you are interested in modifying, as that’s a fairly generic example.

It could indeed be used to similar effect on various bits of event meta data, not just custom (/additional) fields.

[Barry]

Hi William – the guide has already been updated and we will continue to add to it and improve it in response to feedback from users, however most key components are already there.

A great overview of filters is available in the WordPress codex and probably explains it better and in more depth than I can – but the basic idea is to create a function of your own which accepts the current HTML and returns a modified version.

[Barry]

Hi Cynthia, that sounds rather different – could you create a new thread of your own and one of the team will try to help you there (bearing in mind there may be a slight delay due to it being a holiday weekend for many team members)?

Thanks!

[Barry]

The above will basically remove the absolute positioning and width restrictions (which are making it appear is if some text is superimposed on top of other text) and shouldn’t impact on any other areas of your theme.

Thanks!

[Barry]

Can you try editing your theme’s stylesheet and add the following rules to the bottom of that file:

.tribe-events-schedule h3 span {
display: inline;
position: static;
width: auto;
}


[Barry]

Hi Debbie,

This seems to be an issue due to your theme having rules that use absolute positioning for elements like spans within headings. Bear with me and I’ll see if there is a quick answer.

[Barry]

Hi David,

That would indeed seem to be a bug. Let me report this to the devs and hopefully we can get a fix out there sometime soon.

Thanks for your support and patience,

Barry

[Barry]

Hi William,

If you visit Events > Settings > Display you will find an option labelled Disable the Event Search Bar – selecting this brings back the “classic header”.

It may not look identical to those in the old version of the plugin, due to styling differences, but it should get you pretty close and you can then customize it to your heart’s content 🙂

[Barry]

Definitely: just to give you the full picture, those big grey calendar images will be replaced by featured images (if featured images have been assigned) – just in case that changes your mind as it does look quite nice, though I appreciate it may not be everyone’s cup of tea 🙂

Anyway … if you want to remove that section then the easiest way to handle this is simply to add a single line of code to your theme’s functions.php file:

remove_action('tribe_events_single_event_after_the_meta', 'tribe_single_related_events');

They should then disappear. Commenting out or removing the above line will bring them back.

Let me know if that helps/if you need further assistance on this one.

[Barry]

Hi Lyne,

Unfortunately that’s looking like a bug. I’ll report that and get back to you with an update as soon as I can. Now that 3.0 has been released we are returning to our normal habit of releasing regular maintenance updates to catch things like this, so there shouldn’t be too big a delay here.

Thanks!

[Author]

Posts