[Barry]

Hi Jason,

The calendar is extremely customizable so something like this should definitely be achievable. We to tend to be a little limited in terms of how much depth we can go into with customization requests like this, but I can definitely try to point you in the right direction 🙂

In this case, I’d recommend setting up a template override – simply copy the following file:

wp-content/plugins/the-events-calendar/src/views/month/single-event.php

Place the copy inside your theme, ie:

wp-content/themes/YOUR_THEME/tribe-events/month/single-event.php

Now locate the following code:

<h3 class="tribe-events-month-event-title"> <a href="<?php echo esc_url( $link ) ?>" class="url"><?php echo $title ?></a> </h3>

Replace it with the following:

<h3 class="tribe-events-month-event-title">
	<a href="<?php echo esc_url( $link ) ?>" class="url"><?php echo $title ?></a>
	<?php echo tribe_get_start_date( $post->ID, false, 'j M Y @ H:i' ); ?>
</h3>

What we’ve added is an extra line adding date and time information. You could certainly extend this to include other information and add additional HTML to help tweak it on a presentational level, too.

Does that help?

[Barry]

Hi Francisco,

Great question!

You can of course sell different types of ticket for the same event and you can also ‘pool’ their stock by using our global stock functionality (if you are selling tickets via WooCommerce or Easy Digital Downloads, at least).

It sounds like perhaps you need something beyond that, though, and need tools to physically organize seating arrangements – is that correct? If so, I’m afraid nothing like that is currently available via our own plugins.

[Barry]

Hi Keiran,

I couldn’t see your screenshot but I visited you site and did identify the issue you spoke of, which appears to be something of a collision between our CSS rules and those of Avada.

The best way to fix this, if you can, would be via the customizer settings found in the Appearance → Customize admin screen. If you can’t find a way to do that, though, you could add some custom CSS along these lines:

/* Unlinked days */
#tribe-events-content .tribe-events-calendar div[id^="tribe-events-daynum-"] {
    color: teal;
}

/* Linked days */
#tribe-events-content .tribe-events-calendar div[id^="tribe-events-daynum-"] a {
    color: teal;
}

/* Today - unlinked */
#tribe-events-content .tribe-events-calendar .tribe-events-present div[id^="tribe-events-daynum-"] {
    color: white;
}

/* Today - linked */
#tribe-events-content .tribe-events-calendar .tribe-events-present div[id^="tribe-events-daynum-"] a {
    color: white;
}

Numerous plugins are available that can help you to add custom CSS like this, or you could follow the steps described here to setup a tribe-events.css file.

I hope that helps!

[Barry]

Hi Ronald! You are more than welcome to monitor this topic 🙂

If you have any questions of your own, however, or need help that is specific to your own installation, then I’d ask that you create a new topic for those.

Thanks!

[Barry]

Hi Francesco,

We’re happy to help if we can but – in general – we try hard to stick to one issue per forum topic.

With that in mind, would you mind posting this question in a fresh topic? You could then add the private replies there, too, or simply ask staff to refer back to your last two replies in this topic.

Thanks!

[Barry]

Hi Susan,

Thanks for contacting us — that does indeed sound pretty alarming!

If you view the admin events list, do the duplicates show there and if you hover over the ‘edit all’ link, do you notice if they share the same post ID in the URL? For example, if the URL looks like this:

http://example.com/wp-admin/post.php?post=1205&action=edit

Then the ID would be 1205. If all (or most of) the Edit All links for this out-of-control set of events do indeed reference the same ID, we can probably craft a query to kill them all, along these lines:

DELETE 
FROM   wp_posts
WHERE  ID = 12345
OR     post_parent = 12345;

Where, of course, 12345 would be the actual ID in your case (you might use a tool like phpMyAdmin to run this query, if your host provides it).

Does that help at all? Of course, it is always sensible to make a complete backup before directly modifying database entries in this way.

Let me know how you get on or if you need further guidance.

[Barry]

Hi Michael,

That’s a really great question and an interesting idea.

At this time I’m afraid that is not possible. What I’d recommend is posting a feature request – or, if a suitable request already exists – upvoting it:

tribe.uservoice.com

For something like this, though it certainly sounds useful, we’d be keen to get a sense of just how much support there might be for the idea.

[Barry]

Thanks for contacting us — I’m sorry to hear you are still experiencing difficulties.

Right off the bat, though, and using our latest releases, I was unable to replicate the same issue. Here’s what I tried:

• Set the site timezone to Auckland
• Created a new event taking place weekly on Tuesdays for 15 weeks (event timezone: also Auckland)
• I set up an exception per your previous topic – monthly on the second Tuesday

The second Tuesday of the month was indeed excluded. That makes me wonder, is the problem in relation to recurring event series generated before you upgraded to our most recent versions – and can you replicate the same thing with a new event?

Thanks for your patience while we look into this 🙂

[Barry]

Hi Kristen,

What you’ve described is the correct and expected behaviour of each shortcode.

[tribe_events_list] is, essentially, a ‘wrapper’ around our advanced events list widget. Just like the widget itself, it does not support the presence of the Tribe Search Bar.

[tribe_events] is used for embedding our full event views – there again, it imitates a normal view such as events/month or events/list, which also don’t have an organizer option as such.

However! There is a way. You can customize any of our views – the primary method for doing so being the creation template overrides – and the basic process is outlined in our Themer’s Guide:

theeventscalendar.com/knowledgebase/themers-guide

If you need the Tribe Search Bar, it would probably make the most sense to customize our list view templates so that they expose the organizer data you are interested in.

I hope that helps!

[Barry]

Hi Annette,

Thanks for contacting us and I’m sorry to hear you’ve experienced problems.

I would strongly recommend that you update, yes! In general, your plugins should at least share the same ‘base version’ – so for instance, if you use version 4.1.0.1 of The Events Calendar, then Events Calendar PRO and Community Events should also be 4.1.x version numbers (not 4.0.x).

However, all are currently in need of updates as many fixes and enhancements have been made since those versions you are currently using were released.

I hope that helps!

[Barry]

Hi William,

Sorry to hear that!

If you are comfortable adding custom code – either to your own plugin used to house customizations or even to your theme’s functions.php file – you could workaround this in one or both of a couple of ways:

function raise_countdown_limit() {
    return 500;
}

add_filter( 'tribe_events_pro_countdown_widget_limit', 'raise_countdown_limit' );

The above snippet should extend the hard limit and might help you capture the event you are interested in … of course, raising the limit like this can have performance and memory considerations (so you may want to remove it after making the selection).

Alternatively:

function alter_countdown_page() {
    return 2; // If this doesn't work, try 3, 4, ... etc
}

add_filter( 'tribe_events_pro_countdown_widget_paged', 'alter_countdown_page' );

The above snippet works slightly differently. If 250 events are listed in the selector, this will alter the query so that the next 250 are listed instead.

I realize that is arguably less than ideal, but it might provide you with a way of achieving your goal in the short term.

[Barry]

Hi Javier,

Unfortunately we do not expose any sort of user interface to make that kind of change.

Theoretically, though, it would indeed be possible (but would require a customization to be built, or direct intervention in the database records).

I can try to point you in the right direction there, but it’s something we don’t officially support right now and I wouldn’t necessarily recommend it if you’re not comfortable with that sort of work.

Of course, you could certainly propose a new feature to make this easier in the future:

tribe.uservoice.com

[Barry]

Hi Martin,

Thanks for contacting us and our apologies for any confusion.

The venue attribute acts as a ‘flag’ (a bit like an on/off switch). If you set it to a positive value such as ‘1’ then it will include venue details beside each listed event. In this regard, it is not unlike the address and city attributes:

[tribe_events_list address='1' city='1' venue='1']

So, in my above example, we are controlling what information is displayed by indicating we wish the street address, city and venue to be provided for each event. What we’re not doing is asking for a list of events that relate to a venue named or with an ID of ‘1’.

Does that clarify things?

[Barry]

Hi Kevin,

If your question is in relation to ecommerce (ie, WooCommerce) related tickets – rather than RSVPs, which of course are one of the options in the screenshot you shared – I would recommend as an initial step updating to the latest versions of all our plugins.

Right now, based on a look at your system information, you are using out-of-date versions of a number of our plugins.

Let me know if that helps!

[Barry]

Thanks for those extra details!

Unfortunately, I’m no further forward in terms of being able to replicate – on using the very same settings as in your screenshot the result is as expected and there is no displacement as you are experiencing.

I wouldn’t want to cause disruption by means of further testing on your live site, so I wonder if you have a test site available or if you can create one (this could be as simple as installing WordPress in a subdirectory, ie example.com/testwp, which is a pretty fast and easy process with most web hosting control panels).

In that clean test environment – and I do appreciate how similar this is to the troubleshooting you have already done – it would be great to see if you can replicate the same thing with only a default theme and our own plugins running, and nothing else.

If you can, that could be helpful in figuring out if this might be an environmental issue of some kind.

Thanks!

[Author]

Posts