Feature Ideas

Hey there and welcome to our feature request forum for The Events Calendar, Event Tickets and all of the premium plugins we develop provide on TheEventsCalendar.com!

We’re always looking for new and awesome ways to improve our products. We think they’re pretty great out of the box, but we also know that there are often things that could make them even better for how folks like yourself use them in the real world. Our tools help the right people, get to the right place at the right time. How can we improve our products and make them super awesome for you and your users? That’s where we can use your help!

If there are features that our products do not currently support but you think would be a huge added value for you and lots of other people, then please share them here with us. The submission form will walk you through a few quick questions to get the ball rolling.

Before posting your idea, here are a few tips that will help make your request stand out and succeed:

Look to see if someone else has suggested the same idea, or something very similar. Many ideas are being submitted and it’s very possible that another request already exists. In that case, add your vote to the existing request.

Be as descriptive as possible. What does the feature do? Where would it be located? Who would use it? How does this improve the overall experience of managing an events calendar in WordPress?

Use mockups, if possible. Pictures are worth a thousand words and having a visual often brings a greater level of clarity to an idea.

Please not, this is not a place to get support or ask questions about how the plugin works. If you need help, please visit our help desk. If you use our free core plugin, you can post in our forum on WordPress.org.

I suggest you ...

Enter your idea

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

They’re claiming a 30% boost but I ran some tests after migrating test data on a development site with your plugins and I easily got even better performance increase benchmarks! This is a really good idea that you guys would greatly benefit from implementing because the more events that are stored using the current method results with the more bogged down a site becomes. In our case, our events site has become unbearably slow and has to be corrected with a lot of caching and other means to make the site even usable.

A giant way to speed up the performance of events calendar plugin: store the data in dedicated database tables instead of wordpress' post meta.

They’re claiming a 30% boost but I ran some tests after migrating test data on a development site with your plugins and I easily got even better performance increase benchmarks! This is a really good idea that you guys would greatly benefit from implementing because the more events that are stored using the current…

Would you consider combining underscore-before.js and underscore-after.js into one file? Both files are small enough that gtmetrix suggests inlining them, so why separate files? I understand this might not be an issue for some, but one of my sites has over 120 https requests, so combining those files would help.

Before the request is sent to the aggregator api, add a filter so that weird attributes on the event host can be mapped to sane attributes in the aggregator server before they are sent to the receiving TEC calendar

The events calendar has options to show events in widgets and in the calendar. There it always uses the standard wordpress pictures and does not resize them. This is a problem for users, as they have to load a lot of data. It also reduces the page rank at Google.
Therefore I want the plugin to resize the images automatically to save data and rank better in Google.

I’m using JS to add the name of the month as a class to the span.tribe-events-list-separator-month

The goal is to use custom graphics for the month headings instead of text. The JS I’m using is not very foolproof, and only fires when the page is finished loading. I had to hide the “next/prev events” buttons, because they reload the page with ajax, so my JS doesn’t get triggered, and the month headings then “disappear”.

If that span had a class with the month name or month number in it already, I wouldn’t need the JS, and it would work perfectly.

I imagine people could also style their months differently based on the season, etc.

Just a thought. Thanks!

I’m using JS to add the name of the month as a class to the span.tribe-events-list-separator-month

The goal is to use custom graphics for the month headings instead of text. The JS I’m using is not very foolproof, and only fires when the page is finished loading. I had to hide the “next/prev events” buttons, because they reload the page with ajax, so my JS doesn’t get triggered, and the month headings then “disappear”.

If that span had a class with the month name or month number in it already, I wouldn’t need the JS, and it would work perfectly.

The Swagger documation of the events calender REST API mentions the parameter categories. But if this parameter is set in requests the API repsonds with HTTP ERROR 400.
I suggest to extend the API to correspond with the swagger documentation.

Would be great to have the ability to change the slugs/endpoints for the pages generated by the Community Events Plugin.
Even simply adding a filter to the multiple `$router->add_route` lines and the `communityRewriteSlug()` in Tribe\Main.php would go a long way to helping devs better integrate Community Events into their sites.

The most obvious use case is for sites building a User Panel: the ability to move the user's events list to my-account/events, (/add, etc), but any site that has multiple user actions that need to be managed (WooCommerce, BuddyPress/BBPress, the myriad of Directory, Classified, Buy Ads, subscription management, etc) would benefit immensely.

Would be great to have the ability to change the slugs/endpoints for the pages generated by the Community Events Plugin.
Even simply adding a filter to the multiple `$router->add_route` lines and the `communityRewriteSlug()` in Tribe\Main.php would go a long way to helping devs better integrate Community Events into their sites.

The most obvious use case is for sites building a User Panel: the ability to move the user's events list to my-account/events, (/add, etc), but any site that has multiple user actions that need to be managed (WooCommerce, BuddyPress/BBPress, the myriad of Directory, Classified, Buy Ads, subscription management, etc) would…

The current default "Type" for organizers is set to "Person" in the Organizer.php file. It would be nice to have the ability to set this to either "Person" or "Organization". Preferably a metabox in the Organizers admin page to select/set the Type.

This is currently possible as a customization using this method. We are still very interested in implementing this, but it numbers among a hundred+ other great feature ideas on our to-do list, so it could be a little while.

Thanks again for sharing your feedback. Cheers!
- The Modern Tribe Support Team

It would be really useful if I could add description text for custom fields. This text would appear on the admin page probably in small italics underneath the provided Field Label. Currently, I have to access the field by the full label in the code. For example:

This is kind of awkward, especially if I need long/detailed help text. And, it is error prone – if I want to change the help text, I have to change the Field Label, which means I have to change any code that accesses it in the array.

It would be helpful if I could access the $fields array another way, such as:

It would be really useful if I could add description text for custom fields. This text would appear on the admin page probably in small italics underneath the provided Field Label. Currently, I have to access the field by the full label in the code. For example: