The Events Calendar 2.0 is a FREE open source plugin with a rich set of features. The plugin is being actively supported with regular releases and bug fixes. We will not be providing any support for non-paying open source users.
Events Calendar PRO 2.0 is a premium add-on which provides a whole new set of features including recurring events, custom event attributes, saved venues & organizers, advances widgets and a whole lot more. Buying PRO and any add-on entitles you to free updates and active support for 1 year from the date of purchase.
Add-ons are a great way to extend what the plugin can do. All our available free and paid plugins and add-ons can be found over on our main products page.
To stay up to date on new plugin development, beta testing opportunities, and more, you can “Like” our Facebook page or follow us on Twitter. You can also subscribe to our email newsletter at the bottom of this page.
Our requirements are the same as WordPress: we require at least WP 3.1 and PHP 5.2. We always recommend that you update to the latest version of WordPress available.
We’ve got a demo site set up right here so you can check out Events Calendar PRO and our other add-ons. You can also take a look at some of the screenshots from the admin side of things on the PRO product page.
Also, be sure to check out the Event Calendar Showcase which includes some of the coolest implementations of our products on the web. Check out the wide variety of styles, functions, and applications that can happen with The Events Calendar, Events Calendar PRO, and our other plugins.
The best way to get a feel for the admin site of our products is to check out the New User Primers and other resources on our Tutorials page. These include extensive video and screenshots showing the admin interface. At this time we do not have a admin demo that potential users can interact with themselves, although we’re hoping to add something like that in the future.
We have a dedicated support forum for each of our premium plugins. These forums are monitored on week days. That is the best place to pose your questions; not only does our team moderate the forum and provide light plugin support, but other users are always chiming into the the discussions with their own thoughts — which makes for a solid experience on all fronts, and allows a number of perspectives that wouldn’t be present during an email exchange.
It’s worth noting that because we don’t have the bandwidth to provide direct support to users of the free plugin, most of the forum (with the exception of the “Pre-Sales” section) is locked down for anyone other than verified premium users. Anyone can browse, but to ask a question or comment, you need to have a valid account. You don’t have to do anything to become verified other than complete a purchase of an add-on — your account is created upon completing your purchase, and the forum is available to use from there. Access to the support forum will remain valid for 1 year from your date of purchase. If you are a looking for support on our free Events Calendar plugin, you can head over to the WordPress.org forum and post your question there. That forum is not monitored daily but we do check in and try to assist as possible.
The Events Calendar PRO will continue working even when the license has expired. You can buy it once and use it for years until it is so old that it will tell the other plugins stories about having to walk uphill both ways back in those good old days. =)
The license allows you to access to upgrades or support while it is valid. Your license is valid for one calendar year from the date of purchase.
This question has come up quite a bit since the launch of Events 2.0: users who have effectively two sites (a staging site and the live/production site), wondering whether they’ll need to buy two license codes to get the plugin working properly.
We put a blog post together covering this, which you should review, but the short answer is no. Since the license is only needed for accessing support & plugin updates down the road — and doesn’t impact actual functionality — you have two options here. You can either ignore adding the license to your dev site all together, and wait to plug it in until your deploy to production/live. Or, you can add the license to staging and then unlink it from that site at launch time via the License Keys section of your account at tri.be so it’s available for the live site.
Either way, one license is plenty for your staging/live needs.
You sure can! And at a discount, too.
Upgrading a license allows you to go from one license variation to another. For example: if you own a Business license for Events Calendar PRO, you are entitled to updates & support for 3 site running the plugin. You may decide after a few months that you like using the plugin on client work, and would like to have it for future projects (yeah!). The Developer license, you’ve decided — with updates and support for 10 sites instead of 3 — would better meet your needs. Luckily, with our new upgrade feature, you can make the jump seamlessly and without having to buy a second license or reach out to Modern Tribe for an upgrade coupon.
The first step is to log in and navigate to Account Central -> License Keys. When you get there, look just beneath the Renew License button and you’ll see links for any license types to which upgrades are available:
In the screenshot above, you’ll notice “Developer” is the only upgrade type available. This is because you already have a Business license, which is one step below a Developer license. Were you running a Personal license (two steps below a Developer license and one step below a Business license), you’d have options to upgrade to either Developer or Business.
Click the link and you’ll be taken to your shopping cart, where the upgrade has been added. Upgrades cost the price difference between your existing license type and the type you’re upgrading to; for example, if you’re upgrading from a Business license (which costs $100) to a Developer licenses (which costs $250), you’ll owe $150. Apply any coupons you’ve got, proceed to checkout and complete the order process.
When your order is complete, head back to your License Keys. You’ll notice that the license type has been upgraded, and the links below the Renew License button have updated (or disappeared if you’ve just upgraded to a Developer license):
Once you see that, you’re all set to start using the license key on more sites. If you encounter any problems, don’t hesitate to drop us a line.
We process online payments via Stripe, which accepts credit cards. We take Visa, American Express, Mastercard, Discover, and JCB. We do not accept orders over the phone or mail.
Refunds are available only in certain circumstances, during which you’ll need to communicate to our team the issue & why you think you’re entitled to a refund. We’re expecting everyone to read through our FAQs before purchasing the plugin — so if you buy it and aren’t satisfied with the functionality when that was explicitly stated in the documentation, we unfortunately won’t be able to provide a refund. Please also note that we cannot provide refunds in any circumstances if it has been 60 days or more since your purchase.
The Events Calendar is translated into:
- Arabic (ar) coming soon
- Bosnian – Bosanksi (bs_BA)
- Brazilian Portuguese (pt_BR)
- Bulgarian – Български (bg_BG)
- Catalan – Català (ca)
- Croatian – Hrvatski (hr)
- Czech – Čeština (cs_CZ)
- Dutch – Nederlands (nl_NL)
- German – Deutsch (de_DE)
- Finnish – Suomi (fi)
- French – Français (fr_FR)
- Greek (gr_GR)
- Hebrew – עברית (he_IL)
- Hungarian (hu_HU) coming soon
- Italian (it_IT)
- Japanese (日本語 – ja)
- Lithuanian – Lietuviškai (lt_LT)
- Norwegian (norsk) - Bokmål (nb_NO)
- Polish – Polski (pl_PL)
- Portuguese (pt_PT) coming soon
- Russian — Русский (ru_RU)
- Serbian — Српски (sr_RS)
- Spanish – Español (es_ES)
- Swedish – Svenska (sv_SE)
- Ukranian – Українська (uk)
Events Calendar PRO is translated into:
- Arabic (ar) coming soon
- Bosnian – Bosanksi (bs_BA)
- Brazilian Portuguese (pt_BR)
- Bulgarian – Български (bg_BG)
- Catalan – Català (ca)
- Croatian – Hrvatski (hr)
- Czech – Čeština (cs_CZ)
- Dutch – Nederlands (nl_NL)
- German – Deutsch (de_DE)
- Finnish – Suomi (fi)
- French – Français (fr_FR)
- Greek (gr_GR)
- Hebrew – עברית (he_IL)
- Italian (it_IT)
- Norwegian (norsk) - Bokmål (nb_NO)
- Polish – Polski (pl_PL)
- Russian — Русский (ru_RU)
- Serbian — Српски (sr_RS)
- Spanish – Español (es_ES)
- Swedish – Svenska (sv_SE)
Community Events is translated into:
- Croatian – (hr) coming soon
- Czech – Čeština (cs_CZ)
- Dutch – Nederlands (nl_NL)
- French – Français (fr_FR)
- German – Deutsch (de_DE)
- Italian (it_IT)
- Norwegian (norsk) - Bokmål (nb_NO) – coming soon
- Spanish – Español (es_ES)
- Swedish (sv_SE) coming soon
- Polish – Polski (pl_PL) coming soon
Eventbrite Tickets is translated into:
- French – Français (fr_FR) coming soon
- Dutch – Nederlands (nl_NL)
- Finnish – Suomi (fi)
- Italian (it_IT)
- Spanish – Español (es_ES)
- Polish – Polski (pl_PL) coming soon
Facebook Events is translated into:
- Czech – Čeština (cs_CZ)
- German – Deutsch (de_DE)
- Norwegian (norsk) - Bokmål (nb_NO) – coming soon
- French – Français (fr_FR) coming soon
- Polish (pl_PL)
- Dutch (nl_NL) coming soon
WooTickets is translated into:
- Norwegian (norsk) - Bokmål (nb_NO)
- German – Deutsch (de_DE)
- Italian (it_IT)
- Czech – Čeština (cs_CZ)
- French – Français (fr_FR)
- Brazilian Portuguese (pt_BR)
- Greek (gr_GR)
- Polish – Polski (pl_PL) coming soon
- Dutch (nl_NL) coming soon
Note that the translation files above may be in various states of completion and there are no guarantees that all are 100% finished. If you find an incomplete translation for your language and are willing to contribute to finishing it out, we’d love to hear from you. We’re always looking for help building out our translations of The Events Calendar & PRO. Shoot us an email and we’ll hook you up with a discount coupon for the plugin(s) you translate.
Please note that this list was last updated in March of 2013 and languages may have changed since then. Please email us if you have any questions about what languages are currently available. Translation files for languages marked coming soon may be available via email.
There sure is. You can check out the rest of our FAQs, our tutorials page (which includes the super useful New User Primers), our help videos listing, and our documentation page for your coder types. You might also want to browse our forums to see if another user’s experience can shed some light on your project. Got a suggestion for a walkthrough or FAQ question that we haven’t covered yet? Let us know.
Yes; Events Calendar PRO 2.0 is a paid upgrade for all users given how widespread the feature changes are from the 1.x set. Here’s what you get for your money:
- Personal license: Costs $50, allows you to install on 1 site and access support forums & updates for 1 year.
- Business license: Costs $100, allows you to install on 3 sites and access support forums & updates for 1 year.
- Developer license: Costs $250, allows you to install on 10 sites and access support forums & updates for 1 year.
Existing users who signed up for our newsletter before launch are eligible for an upgrade discount. We also have a sponsorship program for qualifying non-profits. If you’re a non-profit feel free to reach out to us.
We’ve been paying special attention to the migration path between a 1.x plugin and 2.0 so that people can click update and have their events show up. To be safe though, you should carefully back up your database before upgrading as life can always offer a bit of adventure when we least expect it.
We’ve upgraded Events to be a custom post type — which is a major change in the open source 1.6.5, where “Events” is just a category within Posts. Got 500 events mixed among your posts and worried about making sure they all carry over to 2.0? Don’t worry about it, our plugin will help you migrate them. Upon installing 2.0, go to the bottom of the settings page which will display if there is existing event content that you may want to migrate:
Once the process is finished, the page refreshes with a confirmation message telling you how many events were converted:
Upgrading from free to paid? Not a problem either. In 2.0, Events Calendar PRO can only be activated if The Events Calendar is already installed. So the experience for upgrading will be effectively identical whether you’re going free-to-free or free-to-paid.
All of our WordPress plugins are licensed under GPL2, as inherited by WordPress (http://wordpress.org/about/license/).
WooTickets used the payment gateways supplied by WooCommerce. The free WooCommerce plugin comes with six basic options: Direct Bank Transfer, Check, Cash on Delivery, Credit Card (via Mijireh) and PayPal.
WooCommerce also has a large number of payment gateway extensions available for purchase that can be used with WooTickets.
We’ve separated the code bases of the two plugins for the 2.0 release, so that PRO is an add-on to The Events Calendar. You can run The Events Calendar without PRO; but PRO cannot work unless The Events Calendar is activated.
We’ve prepared a video walk through the process of downloading, installing & activating both versions. We recommend that you also read through the New User Primer. While you are there, review some of the other help videos to get off to a great start.
The url of your calendar depends on whether the grid/calendar view or list view is your default events view. You can dictuate that under Events –> Settings:
If you’ve set the default view to “Calendar”, the grid view will appear naturally at your site at (yoursiteURL.com)/events/. If you selected list view as the default, going to /events will bring up list view, and you’ll need to hit (yoursiteURL.com)/events/month/ to see the grid/calendar view. If you selected grid view as the default, going to /events will bring up grid view, and you’ll need to hit (yoursiteURL.com)/events/upcoming/ to see the list.
Remember that you can also toggle between both views on the frontend using the buttons that appear in the upper right-hand corner of the frontend events page:
Single Day View
Single day view is a PRO-exclusive feature and is only visible from calendar view. To access it, find a day on the frontend grid view that has at least one event, and click your mouse on the date. In the screenshot below, that would mean clicking the “18″ for “November 18, 2015.” It’ll take you to single day view, which is viewable exclusively as a list.
Note that you can access single day view on dates where there are no events, but it will just give a simple message saying there are no events scheduled for that day:
If you’re using The Events Calendar without the PRO add-on activated, the dates will be unclickable in grid view until you re-activate PRO.
Frontend venue pages are a PRO-exclusive feature, and can be accessed by clicking into an individual entry on the frontend. While free users will see the venue name as plain text, it will appear as a link for PRO users:
When clicked you’ll be taken to the frontend venue page, a new feature for 2.0, that gives the description & location of a venue followed by all events taking plcae there.
Look for the “Account Central” dropdown after logging in at tri.be and click the “License Keys” option. They’ll bring up a list of all your current license keys. It also shows what site the license is being used on, and gives you options to unregister the key from that site, upgrade your license, or renew your license. You can also find your license key in the email you received after your purchase.
Today, once you have Events Calendar PRO 2.0 installed, you can update directly from the WordPres admin. Up until now, this wasn’t possible because Code Canyon — where we’d previously hosted the plugin until 2.0 — didn’t support automatic upgrades with WordPress. We have that in place now.
If an update is available for either The Events Calendar or Events Calendar PRO, you’ll be prompted on the plugins page to apply that update. If the new release is for The Events Calendar, you can update on the spot…if it’s for Events Calendar PRO, note that you’ll need to have your license key entered before the update option becomes available.
Head on over to this tutorial page. Our King of Community, Rob, will walk you through renewing or upgrading your license.
Not currently — as it stands, events can go out but can’t come in. We released iCal export support in 1.1.2 with a patch to it in 1.1.3, for both individual events and full calendar. Simple append /ical to the url. (As you’ll see, we added an iCal import button at the bottom of the page). Google Calendar export exists and is functional as of release 1.2 as well. Exporting from Outlook is not supported at this time but may arrive in a future release. As for the broader question of importing, we are developing on some ideas but don’t have any release dates on the books.
Sure! We’d love to hear what would make PRO more valuable for your needs. Head on over to our Feature Ideas forum to suggest and vote on ideas.
We offer no guarantees that all feature requests will make it, nor which will be included in the next release. We value everyone’s opinion and are always looking to make this plugin better.
Head to Settings –> General on the backend, find the “Week Starts On” dropdown and select the weekday of your choosing. The dropdown is identified below in figure A below, or you can watch a screencast of the process.
Figure A: Changing when the week starts:
Yes. Events Calendar PRO adapts itself to the language your WordPress install is using. It will default to English, unless you run WP in a different language — in which case the calendar will reflect that. The Events Calendar and our add-ons feature translation files for a number of languages. The most recent list of available languages may be found here.
Note that not all of these are 100% complete, so no guarantees that everything will be translated. You may want to update the translation or make a new one if your language is not available. If you are interested in translating for us in exchange for a discount, please send us an email.
If you want to use a language that we have a translation for, here’s how to have WordPress use that translation in your install:
- You’ll need to know your language’s code. Each language has an official code that WordPress uses to reference it, so you’ll want to double check on the language list what code you’re looking for. For example, the code for German is DE_de.
- Make sure the language files you need are in place. Go to wp-content/plugins/the-events-calendar/lang and check the list. There should be two files for each language code, a .po and a .mo file. If your language files aren’t there but the language is on our translation list, send us an email and we’ll look into it.
- Open your wp_config file. Scroll down to line 64 (or thereabouts). It will look something like this:
- Enter your language code after WPLANG. For example, to change your site’s language to German, you would enter de_DE:
If you’re confused about how to change your site’s language by modifying the wp-config.php file, watch this screencast. - Lastly, in your dashboard, go to Settings –> Permalinks and clear your permalinks. You should now see the language you enabled. Keep in mind that translations may not be 100% complete or may only exist for some plugins, so you may still see some English.
Making or updating a translation? Here’s how to translate a plugin using .po files:
- To translate the plugin in your own language first copy the content of the .pot file for either The Events Calendar (/wp-content/plugins/the-events-calendar/lang/tribe-events-calendar.pot), Events Calendar Pro (/wp-content/plugins/events-calendar-pro/lang/tribe-events-calendar-pro.pot) or one of our other add-ons.
- For this example let’s say you were creating a Japanese translation. You would create a new file and name it ‘tribe-events-calendar-pro.jp_JP.po’ (for Pro) and/or ‘tribe-events-calendar.jp_JP.po’ (for the base open source plugin). You can double check that you’re using the correct naming pattern by looking in the /lang folder of the plugin you are translating and comparing the the other files.
- Make any translation changes you want in the .po files and save.
- Next, fire up PoEdit or other program to convert your .po file and open the .po file and then click the Save button in PoEdit to generate the .mo file. If you opened the .po files from the /lang folder for a plugin, you should now have the associated .mo file in the folder as well.
One last point: if you’re just trying to change the title of your calendar, there is no need to edit the .po/.mo files or adjust the language in any way. See our separate FAQ entry for guidance on that simple change.
If you’re using Events Calendar PRO, you’re in luck: the PRO version saves each venue that has been used for events so far, and makes them available for use on all future events. Saved venues appear in a dropdown menu in the “Event Location Details” section of the event creation page:
Assuming you haven’t set a default venue under your Settings page, the dropdown will default to “Use New Venue”. Just click to whatever venue you wish from the dropdown — on doing so, the blank fields will all be replaced. When you see this, you know you’re set:
Remember that if you ever need to modify an existing venue, you can do so by logging on to your sites backend and finding Events –> Venues in the left-hand sidebar. Click into it, click on the name of the venue you want to update and make any changes to it’s description/location data you see fit. Remember to save when you’re done!
Customized defaults are an option for Events Calendar PRO users. Log on to your site’s backend, scroll to Events –> Settings, and click the Defaults tab:
Check the “Enabled” box to turn your customized defaults on, and then fill in the fields below. You can add as many or as few custom default options as you want — in the screenshot above, all I’ve set is a default state (Washington). If I wanted to save even more time on the event creation side, I could set a default organizer or venue so that no location data had to be added in the future.
You can. This option is only available to PRO users, though, since frontend venue pages are a PRO-only feature. Log on to your sites backend, and in the sidebar find Events –> Venues:
Find the venue you want to add a description for in the list, and click into it. The page you’re taken to will look very similar to what you see when creating a new post; beyond the title, you’ll see a regular entry body followed by the venue information below:
The description field is where you can add your location details. It operates just like any other WYSIWYG editor, so feel free to add imagery and otherwise spice up your venue description as you see fit.
If you’re using PRO, there’s a widget built in that will do just this. It’s called the “Calendar” widget; while it is pretty bare bones and doesn’t offer any customization, it does create a simple grid view in your site’s sidebar, like so:
Not at this point — this is an industry standard, and we likely will be keeping it as-is until that changes.
Our Eventbrite Tickets add on is currently set up in such a way that for most customers their ticket price will be translated into USD ($). That isn’t desirable for customers elsewhere, but it can easily be amended by adding a small amount of code to your theme’s functions.php file.
You can find the code here. Note that, as is, that code will set the currency to Euros – to change this, simply follow the instructions in the comments and replace EUR with the appropriate currency code for your jurisdiction.
In The Events Calendar 2.0 and Events Calendar PRO 2.0, we’ve improved the templating framework that ties into the Default Page Template. On your settings page, use the “Events Template” dropdown under the Theme Settings section to control the look & feel of the calendar.
The plugin comes with two of its own standard offerings, and your theme will likely include additional options.
That being said, every theme has slightly different CSS – so while TEC & PRO will not look perfect in every theme, we can get pretty close by being smart about our styles and being explicit wherever possible. We’ve done some heavy testing on Thesis and Genesis, for example, after seeing that a lot of PRO users integrate our plugin with those themes. And the integration has been extremely smooth so far.
If that doesn’t do the trick, just stick closely to the CSS rules that your theme is already using and you shouldn’t have too much trouble. Remember, the output is just HTML with CSS selectors, so you can skin it to fit in your theme by just making our stock template match up with your theme’s page.php template.
The best way to report a bug would be to do so at the support forum for add-ons or the open source forum for free users. You can also feel free to shoot them in an email to our support team. Please note that while we do track reported bugs, support will only be provided in the Modern Tribe forums. Please make sure to always include at least a screenshot/screencast demonstrating the issue and a link to your site if possible.
Before reporting any bugs, make sure you’ve checked to see whether this is actually a problem with our plugin or a conflict with your theme/another plugin. This can be done by just deactivating your other plugins one-by-one and/or reverting back to the default Twenty Twelve theme to see if the issue persists.
If you can’t find the Events URL Slug (and the corresponding Single Event URL Slug), it’s likely because you don’t have a pretty permalink structure — something other than the default, ie /%postname%/ — enabled.
To do so, just navigate to Settings –> Permalinks to make that switch; upon doing so, these slug fields should appear on Events –> Settings.
The input boxes for your license keys can disappear if you are running out-of-sync plugin versions. For example, if you are running The Events Calendar 2.0.9 and Events Calendar Pro 2.0.10, you may not be able to input new license keys. Check your plugin list under the Plugins in the Admin dashboard. The license numbers for The Events Calendar and Events Calendar Pro should match. If they don’t, update as needed and refresh your Settings page. If you’re having trouble downloading or need help, just shoot us an email and we’ll help you get things sorted.
No longer applicable in 3.0, but still a potential issue in 2.x. If the page title has take on the title of the first event, there are a couple of things you can do to fix this.
First, find out what you are using for your Events Template in Events > Settings > Template. Make note of the setting here. If you’ve got the “Default Events Template” option selected, then add the following code to your themes functions.php file and modify as needed to set the titles you want:
add_filter('tribe_get_events_title', 'my_get_events_title');
function my_get_events_title($title) {
if( tribe_is_month() && !is_tax() ) { // The Main Calendar Page
return 'Events Calendar';
} elseif( tribe_is_month() && is_tax() ) { // Calendar Category Pages
return 'Events Calendar' . ' » ' . single_term_title('', false);
} elseif( tribe_is_event() && !tribe_is_day() && !is_single() ) { // The Main Events List
return 'Events List';
} elseif( tribe_is_event() && is_single() ) { // Single Events
return get_the_title();
} elseif( tribe_is_day() ) { // Single Event Days
return 'Events on: ' . date('F j, Y', strtotime($wp_query->query_vars['eventDate']));
} elseif( tribe_is_venue() ) { // Single Venues
return $title;
} else {
return $title;
}
}
If you’ve got the Default Page Template selected, then first try opening up your theme’s page.php file and look for where the_title() is executed. If you don’t see the_title() in page.php, try looking in header.php. It helps to do a find in the file instead of scanning it but I’ll leave that up to you. If you don’t find the_title() in either of those files then it’s either in another template or added dynamically some other way in your theme and you’ll need to track it down. Try looking in your theme’s documentation and look up where the_title() is executed. You may need to contact the theme author.
As an example, in your theme you might find:
<h1><?php the_title(); ?></h1>
or:
<?php echo get_the_title(); ?>
Once you’ve found where the_title() is executed, you’ll want to use these conditional wrappers: https://gist.github.com/2415009 – to help you conditionally set the title for any of the event related pages (look at the comments in the wrapper code). Basically you’re going to want to hard code the title for the calendar (gridview) page similar to the following:
if( tribe_is_month() && !is_tax() ) { // The Main Calendar Page
echo 'Events Calendar';
} elseif( tribe_is_month() && is_tax() ) { // Calendar Category Pages
echo 'Events Calendar' . ' » ' . single_term_title('', false);
} elseif( tribe_is_event() && !tribe_is_day() && !is_single() ) { // The Main Events List
echo 'Events List';
} elseif( tribe_is_event() && is_single() ) { // Single Events
echo get_the_title();
} elseif( tribe_is_day() ) { // Single Event Days
echo 'Events on: ' . date('F j, Y', strtotime($wp_query->query_vars['eventDate']));
} elseif( tribe_is_venue() ) { // Single Venues
echo get_the_title();
} else {
echo get_the_title();
}
Pay attention to any specific code your theme may be using for the title too because you may want to wrap items in HTML and the like. Here is another example from a specific theme where the_title() would be wrapped in HTML markup:
<div id="pageHead">
<?php if( tribe_is_month() && !is_tax() ) { // The Main Calendar Page ?>
<h1 class="home">The Main Calendar</h1>
<?php } elseif( tribe_is_month() && is_tax() ) { // Calendar Category Pages ?>
<h1 class="home">Calendar Category: <?php echo tribe_meta_event_category_name(); ?></h1>
<?php } elseif( tribe_is_event() && !tribe_is_day() && !is_single() && !is_tax() ) { // The Main Events List ?>
<h1 class="home">Events List</h1>
<?php } elseif( tribe_is_event() && !tribe_is_day() && !is_single() && is_tax() ) { // Category Events List ?>
<h1 class="home">Events List: <?php echo tribe_meta_event_category_name(); ?></h1>
<?php } elseif( tribe_is_event() && is_single() ) { // Single Events ?>
<h1><?php the_title(); ?></h1>
<?php } elseif( tribe_is_day() ) { // Single Event Days ?>
<h1><?php $title = 'Events on: ' . date('F j, Y', strtotime(get_query_var( 'eventDate' ))); ?></h1>
<?php } elseif( tribe_is_venue() ) { // Single Venues ?>
<h1><?php the_title(); ?></h1>
<?php } else { ?>
<h1><?php the_title(); ?></h1>
<?php } ?>
</div><!--end pageHead -->
I hope that helps! If you have any questions about this or need theme specific help, please open up a thread in our forum: http://tri.be/support/forums/
You probably haven’t hit the “Enable Google Maps” checkbox on the backend, under Events –> Settings. Once that is enabled you’ll have the option to embed Google maps in your frontend event listings and — if you’re a PRO user — to see a map preview on the backend while creating your new events. Remember that after enabling Google Maps on the backend, you’ll also need to set how it displays (ie embedded in the post; just a button to view at Google Maps; or both) within each event you create.
Chances are you’ve attempted to activate The Events Calendar or PRO when another version of that same plugin is already running. To activate 2.0, make sure all earlier versions of both plugin have been deactivated.
This is a known issue that only occurs with certain themes. Luckily, a user on the WordPress.org forums provided a solution that should do the trick if your theme is impacted.
To start, make a copy of table.php and place it in a newly-created ‘events’ folder in your theme directory. Open the file, and add — directly above the first occurrence of $monthView (on line 31) — the following code:
if( !$eventPosts ) {
$eventPosts = new stdClass();
$eventPosts -> EventStartDate = '2012-'. $month .'-01 00:00:00';
$eventPosts -> EventEndDate = '2012-'. $month .'-01 00:00:00';
$eventPosts = array( $eventPosts );
}
That ought to fix the issue for you!
Don’t worry…this isn’t cause for alarm. When creating categories, the slug automatically adds a -2 when a category or tag with that same name already exists in the system. Still confused? Check out our screencast on the matter.
These are just notices to help our team test and are nothing to be concerned about. You shouldn’t run wp_debugging on live sites, as little notices like that are just for dev purposes and can put the site’s overall security at risk.
There’s an option for both free and PRO users, which can be found under Events –> Settings.
On the General Settings tab you’ll see a “Multiday Event Cutoff” option with a dropdown featuring times from 12 – 11:30 a.m.
By default, this will appear to 12 a.m. But you can change it to a later time if that meets your needs; for example, if your event goes from 8 p.m. Friday to 1:30 a.m. Saturday, you can keep it from appearing in grid view as a Saturday event by setting the dropdown to 1:30 a.m. or later. The example above shows what happens when the dropdown is set to 2 a.m.; in this situation, the Friday-Saturday event would only appear on the calendar on Friday.
The plugin should use the date/time format you’ve specific in Settings > General. You can override this by modifying the template views. For any of the template views that display the start or end date & time for an event you can simply pass in PHP date strings to re-format the date/time. To modify template views, please see our Themer’s Guide. In general though, if you see one of the start or end date & time functions (tribe_get_end_date() or tribe_get_start_date()) you can simply pass in the PHP date string in the third argument slot in the function to re-format the date like so:
echo tribe_get_start_date( $post->ID, false, 'D. M j, Y' );
That would display the start date like: Mon. Jan. 15th, 2012
To add the time, just change the second argument to true to display the time:
echo tribe_get_start_date( $post->ID, true, 'D. M j, Y' );
That would display the start date like: Mon. Jan. 15th, 2012 6:00pm
Some users have reported that, when they upgraded from The Events Calendar 1.6.5 to The Events Calendar 2.0, their fixed hour range events automatically became all day events. This is unfortunately a known issue that was caused by a bug in 1.6.5 and how it interacted with WP 3.2, to which there is no remedy. Make sure you’ve backed up your events before migrating.
Just add this to your theme’s functions.php to include events on the home page:
add_filter( ‘pre_get_posts’, ‘include_events_on_home’ );
function include_events_on_home( $query ) {
if ( is_home() && false == $query->query_vars['suppress_filters'] )
$query->set( ‘post_type’, array( ‘post’, ‘tribe_events’, ‘attachment’ ) );
return $query;
}
Thanks to Justin Tadlock, without whom we would have had a much harder time getting this nailed down 
We’ve got a whole tutorial on how and when to use template overrides. Check it out!
No. This plugin works by rewriting the loops and doesn’t use shortcode embeds for the time being.
It is not possible to install multiple instances of Events Calendar on one site. The easiest way to make multiple calendar is to use different categories within the plugin: set up each “calendar” as a different category, then link to those category filtered calendars from the header menu. Not sure how to find an event’s category? Click into the individual event entry and click the category hyperlink that appears under the event details — from there, snag the URL of the page you’re taken to and you’ll be set. You can see how to set event categories while writing your post in figures 22a & 22b, below, or watch this brief screencast to see the full process.
Figure a: Setting up calendar categories:
Figure b: Getting the category URL:
There isn’t a stylesheet for printing, as plugins don’t typically come with print stylesheets unless it’s a plugin that actually creates and inserts one for you. But, you’d actually want to do this via a print stylesheet in your theme… this is a pretty good guide on how to do that. Basically, in the print stylesheet you can input all the specific calendar styles you want to have set up for print.
As you may already know, you can access your Events RSS feed at http://your-url.com/events/feed/ or http://your-url.com/events/category_name/feed/ if viewing an event category (replace ‘events’ with whatever your events slug is). The feeds do not automatically include the event start and end date/times, but you can easily add these by tapping in to the WordPress feed hooks. To add the event start and end date/times, add the following to your theme’s functions.php file:
// Add Tribe Event Namespace
add_filter( 'rss2_ns', 'events_rss2_namespace' );
function events_rss2_namespace() {
echo 'xmlns:ev="http://purl.org/rss/2.0/modules/event/"';
}
// Add Event Date to RSS Feeds
add_action('rss_item','tribe_rss_feed_add_eventdate');
add_action('rss2_item','tribe_rss_feed_add_eventdate');
add_action('commentsrss2_item','tribe_rss_feed_add_eventdate');
function tribe_rss_feed_add_eventdate() { ?>
<ev:tribe_event_meta xmlns:ev="Event">
<?php if (tribe_get_start_date() !== tribe_get_end_date() ) { ?>
<ev:startdate><?php echo tribe_get_start_date(); ?></ev:startdate>
<ev:enddate><?php echo tribe_get_end_date(); ?></ev:enddate>
<?php } else { ?>
<ev:startdate><?php echo tribe_get_start_date(); ?></ev:startdate>
<?php } ?>
</ev:tribe_event_meta>
<?php }
There is no limit to any other information you want to add to your events feed. For more information on customizing feeds, I highly recommend this article.
The following capabilities are available for use when registering a new WordPress role:
Events
edit_tribe_event
read_tribe_event
delete_tribe_event
delete_tribe_events
edit_tribe_events
edit_others_tribe_events
delete_others_tribe_events
publish_tribe_events
edit_published_tribe_events
delete_published_tribe_events
delete_private_tribe_events
edit_private_tribe_events
read_private_tribe_events
Venues
edit_tribe_venue
read_tribe_venue
delete_tribe_venue
delete_tribe_venues
edit_tribe_venues
edit_others_tribe_venues
delete_others_tribe_venues
publish_tribe_venues
edit_published_tribe_venues
delete_published_tribe_venues
delete_private_tribe_venues
edit_private_tribe_venues
read_private_tribe_venues
Organizers
edit_tribe_organizer
read_tribe_organizer
delete_tribe_organizer
delete_tribe_organizers
edit_tribe_organizers
edit_others_tribe_organizers
delete_others_tribe_organizers
publish_tribe_organizers
edit_published_tribe_organizers
delete_published_tribe_organizers
delete_private_tribe_organizers
edit_private_tribe_organizers
read_private_tribe_organizers
There are numerous ways to hide and move around elements in the dashboard. I would highly suggest two plugins for this, both of which are available on the WordPress.org plugin repo:
Taking this course of action involves two steps. (We’re going to use Adminimize in this example, but keep in mind that Admin Menu Editor has a nice PRO version which — if you were to purchase — offers slightly nicer controls for this task.)
First, download and install Adminimize from the link above or via WordPress and activate it. Then go to Settings > Adminimize and deactivate the Events menu for any user groups you want. You’ll also see that you have control over a lot of other things for your users with this plugin.
Second, add this code to your theme’s functions.php file which will hide the Events admin bar drop down for non-administrators:
// show events menu in admin bar only for admins
if (!current_user_can('manage_options')) {
define('TRIBE_DISABLE_TOOLBAR_ITEMS', true);
}
You’ll need to modify it if you need specific control for certain groups. You can find more out about how to do that by looking at the documentation for current_user_can.
By default the dates in the mini-cal widget are not linked to those days. To link the days, make a copy of /wp-content/plugins/the-events-calendar/views/table-mini.php and place in an ‘events’ folder in your theme. Then replace line 127 with the following:
//set mini cal days as links
if( function_exists('tribe_get_linked_day') ) {
$date = tribe_get_start_date( '', false, 'Y-m-'.$day.'' );
$return .= ( count($monthView[$day]) ) ? "<a href='" . tribe_get_day_link($date) . "' class='tribe-events-mini-has-event'>$day</a>" : $day;
} else {
$return .= ( count($monthView[$day]) ) ? "<a class='tribe-events-mini-has-event'>$day</a>" : $day;
}
We’ve got you covered! Check out this handy tutorial.
There is. Just add the following to your functions.php file:
function run_init() {
register_taxonomy_for_object_type('post_tag', 'tribe_events');
}
add_action('init','run_init');
This will enable tags within events on the backend. To get the tags to display, you can use something like:
$terms = get_terms("post_tag");
$count = count($terms);
if ( $count > 0 ){
echo "<ul>";
foreach ( $terms as $term ) {
echo "<li><a href='/tag/" . $term->slug . "'>" . $term->name . "</a></li>";
}
echo "</ul>";
}
Replace ‘tag’ with the tag base for your website.
Also, add this to your functions.php file to include events in your tag archives:
function include_in_tags( $query ) {
if ( $query->is_tag ) {
$query->set( 'post_type', array( 'post', 'tribe_events' ));
}
return $query;
}
add_filter( 'pre_get_posts', 'include_in_tags' );
NOTE: This approach does not include a solution to set tagged events with your events based slug. We will be including more robust event tagging in our upcoming 3.0 release.
Currently, the calendar view does stretch dynamically, although it may or may not gracefully pop into your template. The rest of the views use percentage based widths and should respond well, but there may be specific things you will need to adjust at different screen size breakpoints.
As of version 3.0, we’ve made some improvements to how the plugin responds at different screen sizes. As in previous versions, all of the views use percentage based widths for elements; that will allow them to respond to different screen sizes. We’ve made some further adjustments to the views so they look even better now at different resolutions. That being said, if your theme is not responsive; you likely won’t notice much responsiveness anyway. If there are specific responsive actions or display preferences you would like to take place, you will need to code them yourself.
This plugin doesn’t include any setting to control padding on a featured image. But you can still include it by adding some CSS or using a custom theme to support padding. Or, just upload it from your computer with the necessary padding already built in.
This is doable using a PHP include. Simply add the following in any of your theme templates or via another function and it’ll display accordingly:
include('wp-content/plugins/the-events-calendar/views/gridview.php');
We’ve got a quick tutorial to walk you through the process.
This is set on the backend, under Settings –> Reading: “Blog pages show at most: (x) posts.” Note that this will impact both the calendar and any other loops you have on the site. How to find this section can be seen below in figure A, and we’ve also put together a screencast that walks through the whole process.
Figure A: Changing how many posts dislay on /events:
Sure can.
First, make sure you are overriding the ECP templates by creating an ‘events’ folder in your theme directory. Then make a duplicate copy of gridview.php in that same ‘events’ folder and then find the code around line 18 that looks like this:
Move that chunk of code wherever you want into the footer. You might have to do a little CSS’ing to get it looking right though.
The basic time display settings are controlled by your WP install, under Settings –> General. Whatever you configure there will carry over to both regular WordPress posts and your events.
The easiest way to do this would be to simply edit the English translation file and make sure that change carries over to the live site.
These options cannot be removed from the admin bar without potentially breaking the entire plugin in the process. As a workaround, just change the permissions on the Organizer/Venue custom post types so that only admins (or whatever level of access you deem appropriate) can see them. This won’t carry over to EventCategories, but will keep Organizer and Venue data locked down.
Not out of the box, no. The template is easy enough to overwrite with a custom template, though, so you can get there with the right coding skills.
Maps embedded in an individual event listing should not appear in list view – they’ll only show up when you click into the individual entry. Calling in maps to display on list view would require a heavy amount of custom development, and runs the risk of causing Javascript problems across your site. It’s probably best to leave this as-is unless you are extremely well-versed in WordPress development.
We do have an API that allows you to add, edit, delete or query for events. The API that we have exposed is essentially made up of functions that you can call to build events or extend Events Calendar PRO.
We’ll have a list of the hooks & filters you can use to access this API very shortly.
Sure, take a look:
- _EventShowMapLink
- _EventShowMap
- _EventAllDay
- _EventStartDate
- _EventEndDate
- _EventVenueID
- _EventShowMapLink
- _EventShowMap
- _EventCost
- _EventOrganizerID
- _EventPhone
- _EventRecurrence
- The Venue Custom Post type uses:
- ‘_VenueVenue’,
- ‘_VenueCountry’,
- ‘_VenueAddress’,
- ‘_VenueCity’,
- ‘_VenueStateProvince’,
- ‘_VenueZip’,
- ‘_VenuePhone’
- The Organizer Custom Post type uses
- ‘_OrganizerOrganizer’,
- ‘_OrganizerEmail’,
- ‘_OrganizerWebsite’,
- ‘_OrganizerPhone’
Yes! While users of ECP were previously limited to just the few event settings we’d hardcoded in, those days are now a thing of the past. Now, site administrators have an option in the settings panel to add additional meta fields of their choosing, beyond the defaults.
To first configure your custom meta, you’ll log in to the backend and go to Events –> Settings. Click the Additional Fields tab up at the top:
You’ll notice right off the bat that there’s a “Field Label”, “Field Type”, and “Options.” Field Label just dictates what you want the new item to be labeled as. Upon publication it will appear alongside your event details up where start time, end time, etc. can be found. Field Type gives the choice of selecting how you want this new custom meta to be configured on the backend — your options include text fields, radio buttons, checkboxes, etc.
The Options section is where, if you picked a multi-choice field type like checkboxes or radio buttons, you’d add (on separate lines) each of the options you want to have available when creating new events:
In the example above, you’ll see we have configured a text field for the host — assuming that whoever creates the event will know the name of it’s host and can enter that in — and a checkbox field for the raffle prizes being given away, with the 3 prize options listed in the Options box.
Upon saving and navigating over to create a new event, you won’t notice anything majorly different about the page structure — you still start with your title/entry body, then get down into the event date / time / venue / organizer. But scroll to the bottom of the event details section and you’ll see the meta fields in action:
There, you’ll see that the author of this event now has a space to add the extra details not covered above when setting the date, venue & organizer. This event looks like it’s going to be a celebration: the host has been defined as local celebrity Johnny Jones, and 2 of the 3 raffle prizes are up for grabs. Sweet!
It all comes together upon publication. At the top of the event listing, where the rest of the event basics are displayed, our new meta fields can be seen. What previously was limited to looking like this:
Is now much more robust, and appears like so:
You can add multiple meta fields as you see fit, and can use any combination of choices from the “Field Type” dropdown. These new fields will appear on any event created within your site going forward, until someone removes them from the list of additional fields at Events –> Settings. They will of course not show up on the frontend unless you configure them accordingly on the backend when creating your event…so no need to fear their constant presence on events where it isn’t appropriate.
Even better — for all intents and purposes to your frontend users, there’s no difference between this and the hardcoded options that came with the plugin fresh out of the box.
Easy — though not something we’re covering here. Instead, check out the the tutorial our developer Jonah was kind enough to put together walking through this very process.
