FAQS

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.

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, 1 license is plenty for your staging/live needs.

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.

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 have a sponsorship program for non-profits to find a way to get them the plugin at a charge that isn’t painful. If you’re a non-profit feel free to reach out to us and get on the wait list.

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.

Our requirements are the same as WordPress: we require at least WP 3.1 and PHP 5.2. It is likely that as of The Events Calendar/Events Calendar PRO 2.1, we will require WordPress 3.3 (but this has not yet been solidified as of 1/19/12). For now, WP 3.1 and PHP 5.2 should cover you.

We’ve got a 2.0 demo site set up for users to check the plugin out, right here. Looking to see a specific feature in action, and not finding it on the demo site? Shoot us an email and he’ll try to get it configured for you.

* The demo site will not be up until a week or two after launch.

Yes! Our support forum has a thread specifically dedicated to letting users showcase their sites, which you’re more than welcome to peruse. Feel free to add your site to the discussion…so long as you don’t mind a bunch of preying eyes checking out out or other users asking how you did it.

In addition, we’ll be highlighting sites that use ECP in creative ways at our Facebook page. Might be worth becoming a fan, if you haven’t already, so you’re in the loop when those updates come around.

Currently you can pay using Paypal. We do not accept orders over the phone or mail.

If you’re interested in upgrading from a personal license to a business or developer license, drop us a note and we’ll work with you to make the upgrade happen.

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. Please note that 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.

The Events Calendar is translated into:

• English
• Bulgarian [BG]
• German [DE]
• Greek [GR]
• Italian [IT]
• French [FR]
• Spain Spanish [ES]
• Swedish [SE]
• Brazilian Portuguese [BR]

Events Calendar PRO is translated into:

• English
• Bulgarian [BG]
• German [DE]
• Greek [GR]
• Italian [IT]
• French [FR]
• Spain Spanish [ES]
• Brazilian Portuguese [BR]

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 in exchange for the translation.

Add-ons are small supplemental plugins that expand your events calendar’s capabilities. These add-ons range in price from $10-100 a piece. You must first activate either The Events Calendar 2.0 before you can begin using an add-on.

We’ll have more specifics on our add-ons as we gear up to release them in the coming months. To make sure you’re kept in the loop, why not sign up for our newsletter (at the bottom of the site)?

All of our WordPress plugins are licensed under GPL2, as inherited by WordPress (http://wordpress.org/about/license/).

We have a dedicated support forum, which is 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 “Welcome” threads) is locked down for anyone other than verified Add-On 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.

There sure is. Beyond this pre-purchase FAQ, we’ve also got a number of FAQs, a help video sections Support center, documentation for you coder types and what will quickly be a thriving forum. Got a suggestion for a walkthrough or FAQ question that we haven’t covered yet? Let us know.

Add-ons are a great way to extend what the plugin can do. All our available free and paid plugins & add-ons can be found over at the Shop page.

To stay up to date on new plugin development, beta testing opportunities and more, it’d probably be a good idea to “Like” our Facebook page or follow us on Twitter.

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. You can check that out right here. While you are there, review some of the other help videos to get off to a great start.

Grid View

Whether grid view is your default events view will depend on whether you’ve configured it as such under Settings –> The Events Calendar:

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.

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:

List View

Whether list view is your default events view will depend on whether you’ve configured it as such under Settings –> The Events Calendar:

If you’ve set the default view to “Event List”, the list view will appear naturally at your site at (yoursiteURL.com)/events/. 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 in “calendar” (grid) view. To access it, after activating The Events Calendar & PRO, find a day on the frontend grid view that has at least 1 event:

Then, simply click your mouse on the date itself within the box — in the above screenshot, that would mean clicking the “15″ for “November 15, 2015.” It’ll take you to single day view, which is viewable exclusively as a list (viewing in the grid is currently not an option for single day view).

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.

Just find 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 and will show which of those are in use versus available. You can also find your license key on the “Thank You” page that appears after completing your order.

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.

Sure! We’d love to hear what would make PRO more valuable for your needs. If you shoot an email to pro@tri.be or post a comment on the forum, we’ll make sure it gets added to the list for future discussion. 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.

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:

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. Events Calendar PRO currently features translation files for the following languages:

• BG [Bulgarian]
• DE [German]
• GR [Greek]
• IT [Italian]
• FR [French]
• ES [Spain Spanish]
• SE [Swedish]
• BR [Brazilian Portuguese]
• NO [Norwegian Bokmal]
• NL [Netherlands]
• PL [Polish]
• RU [Russian]

Note that not all of these are 100% complete, but instead are in various stages of completeness and so no guarantees that everything will be translated.

1. 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) or Events Calendar Pro (/wp-content/plugins/events-calendar-pro/lang/tribe-events-calendar-pro.pot).
2. 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).
3. Make any translation changes you want in the .po files and save.
4. 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 either plugin, you should now have the associated .mo file in the folder as well.
5. Then you need to tell WordPress which language to use by modifying your wp-config.php file. Open it and find the line for define(‘WPLANG’, ”); and change to include the identifier for your language, i.e. define(‘WPLANG’, ‘jp_JP’);
6. If you’re confused about how to change your site’s language by modifying the wp-config.php file, watch this screencast.
7. Finally, visit Settings > Permalinks to clear your permalinks and now you should see your translations!

Don’t see your language listed above? If you want to help translate, you’re more than welcome to – feel free to fill out a PO file using PoEdit and send it our way. We’ll gladly offer a personal license in exchange for a completed translation.

Not at this point — this is an industry standard, and we likely will be keeping it as-is until that changes.

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, that’s still open for discussion but we have no plans to implement this currently on the books.

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!

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.

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 event description as you see fit.

Customized defaults are an option for Events Calendar PRO users. Log on to your site’s backend, scroll to Settings –> The Events Calendar, and scroll to the “Customize Defaults” section:

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.

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 Settings –> The Events Calendar.

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

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 the 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 2011 theme to see if the issue persists.

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.

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.

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.

It is. This code should allow you to check whether it’s an all-day event in the loop: if (tribe_get_all_day()) { // do something.

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.

You can change the date format by using this code and replacing the format string with whatever you want to call: echo ‘<p>’.date(‘F j, Y’,strtotime($e->EventStartDate)).’</p>’;

There’s a workaround for both free and PRO users, which can be found on Settings –> The Events Calendar. Towards the top of the page, you’ll see a “Multiday Event Cutoff” section where there’s 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. Thursday to 3 a.m. Saturday, you can keep it from appearing in grid view as a Saturday event by setting the dropdown to 3 a.m. or later. The example above shows what happens when the dropdown is set to 4 a.m.; in this situation, the Thursday – Saturday event would only appear on Thursday & Friday.

You probably haven’t hit the “Enable Google Maps” checkbox on the backend, under Settings –> The Events Calendar. 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.

On editing list.php you could add that you’ll want to remove this while block of code from lines 16-22:

<div id='tribe-events-calendar-header' class="clearfix">
	<span class='tribe-events-calendar-buttons'>
		<a class='tribe-events-button-on' href='<?php echo tribe_get_listview_link(); ?>'><?php _e('Event List', 'tribe-events-calendar')?></a>
		<a class='tribe-events-button-off' href='<?php echo tribe_get_gridview_link(); ?>'><?php _e('Calendar', 'tribe-events-calendar')?></a>
	</span>
</div><!--tribe-events-calendar-header-->

That ought to do it!

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.

The Events Calendar comes with a default stylesheet file and templates for different views and widgets, tailored to the Twenty Eleven theme. Template overrides provide the ability to make copies of these files and modify them in your own theme, preserving your changes the next time you update the plugin.

If you would like to alter the stylesheet or any of the templates, simply create a new folder labeled “events” in your theme directory and copy over any of the files from within the plugin’s views folder (wp-content/plugins/the-events-calendar/views/). The plugin’s stylesheet, events.css, is located in wp-content/plugins/the-events-calendar/resources/.

In addition, if you are running the PRO plugin there are additional templates in its views folder (wp-content/plugins/events-calendar-pro/views/). Following is a list of all the files (including PRO) that you can override:

• events.css (located in the plugin’s /resources directory)
• ecp-page-template.php
• ecp-single-template.php
• events-list-load-widget-display.php
• full-address.php
• gridview.php
• list.php
• single.php
• table-mini.php
• table.php
• events-advanced-list-load-widget-display.php (PRO)
• single-venue.php (PRO)
• widget-featured-display.php (PRO)

Feel free to mix files from free & PRO in the same folder. Then, edit the new files to your heart’s content. Please do not edit any of the above files in the plugin folder(s) as you will lose any of your changes the next time you update the plugin.

Keep in mind that there may be additions or changes to the core plugin templates files or CSS that will not be migrated to the copies you have made. In this case, you will need to manually go through the files you’ve modified to determine what is different and how to implement the core changes.

No. This plugin works by rewriting the loops and doesn’t use shortcode embeds for the time being.

A few users who are using Events Calendar PRO on client websites have asked if there’s an easy way to turn off the upsell — which promotes additional functionality in the form of plugin add-ons — on their installs. The upsell appears both on the individual event admin panel and at the top of the settings page (examples of  both below).

If you’re using 2.0.1, there’s a bit of code you can now add to your wp-config file that will hide both the messages above. Add this:

define('TRIBE_HIDE_UPSELL', true);

Changing the ‘true’ to ‘false’ will bring the upsell back; it’s only hidden when ‘true’ is in place.

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 2.1

The calendar view does stretch dynamically, although it may or may not gracefully pop into your template. We’ve built the default template to work with 2011 default WordPress theme, but you may need to use a custom template to adjust the specifics.

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 template tags. (For more of our template tag documentation, go here). Embedding a given month’s calendar into a page is as simple as adding < ?php tribe_calendar_grid(); ?> in any template; it’ll display accordingly.

To accomplish this $cityregion variable breakout, you can use tribe_get_city(), tribe_get_address(), etc. Don’t forget to check all the functions inside the /the-events-calendar/public/template-tags/venue.php, too.

first make sure you are overriding the ECP templates by creating an ‘events’ folder in your theme directory and then place a duplicate copy of views/single.php in there. That way when you update your changes will remain.

Then, around line 90 take the code:
if ( function_exists('has_post_thumbnail') && has_post_thumbnail() ) {
the_post_thumbnail();
}

and place it below the_content() or wherever else you want it to appear.

Let’s assume you’re working with code along these lines:

$posts = tribe_get_events();
foreach($posts as $post) {
if(tribe_is_multiday()) { ?>


}

From there, you can use the tribe_is_multiday() function wrapped around your query. For example:
$events = tribe_get_events();
foreach($events as $event):
$event_meta = tribe_get_event_meta();
$event_image = wp_get_attachment_image_src( get_post_thumbnail_id( $event->ID ), 'single-post-thumbnail' );

$event_address = tribe_get_full_address($event->ID);

That should get you where you need to be.

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 33 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.

You can. The best and easiest way at this point is to do so using CSS. Place the following CSS in a copy of /wp-content/plugins/the-events-calendar/resources/events.css placed in an ‘events’ folder in your theme:


.events-archive .tribe_events .entry-title,
.tribe-events-cal-title {
position: absolute;
overflow: hidden;
clip: rect(0 0 0 0);
height: 1px; width: 1px;
margin: -1px; padding: 0; border: 0;
}


This will hide the title on the grid and list view but retain it on single events. It’s also still making the title accessible by screen readers and search engines which is better than just setting display: none. See here for more info on this technique.

This should cover a broad range of themes but if it’s not working for you, try changing the .entry-title target to suit your theme. If you’re still having issues, hit us up in the forums.

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.

Since The Event Calendar uses taxonomies for categories you simply need to query for that particular taxonomy and spit out the records. This should do it: https://gist.github.com/2019513

Just put the code at the top of your gridview.php template file. Make sure you first setup a template override for gridview.php if you haven’t already by creating an ‘events’ folder in your theme directory and copying gridview.php in there. This will allow you to retain your changes to it when you update.

Yes. For PRO users, on the backend, visit Settings –> The Events Calendar, scroll down to “Customized Defaults” and select “Enable,” then fill in the requested default fields. When you go to set up events in the future, these fields will be automatically populated with these default values.

The easiest way to do this 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:

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.

This should be possible. We are using the jQuery UI Datepicker, so you could add custom javascript to tie into the text field.

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 you can completely customize the look of this but it’s going to take some CSS skills. Here are the basics:

1. You’ll first want to create your own copy of the events.css stylesheet so next time you update you don’t lose your changes. To do this just create a copy of ‘plugins/the-events-calendar/resources/events.css’ and place into an ‘events’ folder in your theme directory. So if you’re theme is in a folder ‘my-theme’ you would add the events folder so you would have ‘my-theme/events’.
2. Then you’ll want to focus on the Sidebar Calendar styles which can be found around line 436 in events.css – in particular look at line 472 for .tribe-events-calendar-widget .tribe-events-tooltip – that is the CSS selector for the wrapper of the tooltip.
3.  There are a lot of things you could do with the styling and it depends on your particular design and CSS skills for what you can accomplish but the skies the limit. As an example if you wanted to add a light grey background to the tooltip you could add:

.tribe-events-calendar-widget .tribe-events-tooltip {
width:100px;
left:0;
text-align:left;
padding:5px 10px;
background: #efefef;
}

That should give you a pretty good start but keep an eye out in the near future for tutorials on this type of thing.

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 Settings –> The Events Calendar. Scroll to the bottom of the page and find the “Additional Fields” section:

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 Settings –> The Events Calendar. 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.