[Barry]

You could either edit one of your templates and wrap it in <script> tags or – perhaps more “correctly” – you would enqueue it using the WordPress API:

http://codex.wordpress.org/wp_enqueue_script

I’m afraid however we can’t really spare much time to talk through that in detail – and the above link probably does a better job of explaining this than I can.

Definitely though feel free to add a note on our UserVoice page if you feel there is a good case for making the datepicker date formats more flexible via our plugin’s settings page – it would also be interesting from our perspective to see how many others might be in support of this:

https://tribe.uservoice.com/forums/195723-feature-ideas

[Barry]

Hi Sam: I think we posted around the same time. To be clear, I have finished troubleshooting for the time being.

[Barry]

Please bear with me – I’m just seeking help from one of our resident CSS gurus.

[Barry]

Correction! As of 3.0 we have a minimum requirement of WordPress 3.5 – so that probably is indeed the problem here.

[Barry]

Thank you!

There are a few updates you need to make – before you do anything though can I ask you to consider updating WordPress to the latest version first of all and see if that resolves this?

Though I believe it should work with your current version I think there may have been an oversight in relation to how media is handled and that may be the crux of this problem.

* As before, do take the time to make a backup
* Remember that a backup is useless if you do not know how to restore it!

For the time being though I’m finished troubleshooting and will ask your permission if I need further access – so feel free to remove that user account and double check all settings were restored, etc.

Thanks!

[Barry]

That makes sense – I think we’ve got a good starting point for fixing this and it’s just waiting on further action by the dev team at this point 🙂

[Barry]

Ordinarily the featured image on single event pages is indeed the full-sized image, so yes that is what will be linked to.

If that isn’t the case with your theme/set of plugins then something else may be at work. I did visit the URL you provided when you opened this thread but couldn’t locate your events – can you provide a link to a live example?

[Barry]

If you have a complete backup then yes you could restore it to exactly the same point as it was before – we have an FAQ that could give you some guidance here: https://theeventscalendar.com/faqs/help-i-upgraded-but-its-causing-me-problems-how-can-i-downgrade-to-a-pre-3-0-version/

Is there any other way we can help without you having to do that – what are you trying to achieve? I was slightly puzzled as your first post mentioned a little image next to the event countdown, however the event countdown is a new widget as of 3.0.

[Barry]

OK, I ran through those very steps and couldn’t replicate this. Is it possible something else is conflicting – have you tried doing this only with The Events Calendar, Community Events, WooCommerce Tickets and WooCommerce itself along with a default and unmodified theme such as Twenty Twelve?

Does the problem persist at that point and does that allow you to isolate a conflict anywhere?

I do see you noted down that you had tried these steps when you opened the ticket, but since I cannot replicate this I would like to be double check this.

[Barry]

OK, so can you try adding this snippet to your theme’s functions.php file? This should place the title in the grey or “striped” area as it is when other posts/pages display in your theme.

Do note that this also means the title will be duplicated slightly lower down. To get rid of this second title you could override the relevant templates and simply comment out or delete the relevant line.

In single-event.php for instance this looks like:

<?php the_title( '<h2 class="tribe-events-single-event-title summary">', '</h2>' ); ?>

And in month/content.php it looks like:

<h2 class="tribe-events-page-title"><?php tribe_events_title() ?></h2>

For an overview of theming and template overrides in general, please see: https://theeventscalendar.com/support/documentation/events-calendar-themers-guide/

Does that help?

[Barry]

Definitely. As it turns out this is something that is already on our issue tracker, so I’m just waiting for some clarification as to what’s happening on this one and will get back to you as soon as I have that.

[Barry]

OK, so in that case it will call the header.php and footer.php templates and since in most themes the menu will be incorporated into the header.php template there will be no problem.

I’m surprised though that it doesn’t work with the Default Page Template – can you change it to that setting so I can take a look and see if there are any obvious clues?

[Barry]

Thanks for the kind words 🙂

I can’t actually replicate the problem you have described – if I have an event that begins in September this year and ends in July next year, or even a more compact example, it behaves as expected.

Is it possible this is due to a conflict somewhere along the line with your theme or another plugin, or can you show me a live example?

We’d love to help and resolve this if we can.

[Barry]

OK. Well again this can be accomplished by CSS. Where you previously added:

#post--9999 #tribe-events-header,
#post--9999 .entry-title {
display: none
}

Can you make this:

#post--9999 #tribe-events-header,
#post--9999 #tribe-events-bar,
#post--9999 .entry-title {
display: none
}

Note that there are other ways and arguably better ways to do this, but this approach should provide a quick and effective workaround for the time being.

[Barry]

That definitely looks odd.

I notice that you noted down you had tried deactivating all non-Modern Tribe plugins and also, at the same time, switching to a default and unmodified theme such as Twenty Twelve.

Did that resolve this/help you to isolate any component in particular that might be causing a conflict?

[Author]

Posts