[Josh]

Hey Pascal,

Thanks for reaching out to us!

You can take a look at the src > Tribe > importer.php file where the import is defined to determine which sections you would like to remove and utilize the filters there to prevent those from importing.

For example, you should be able to prevent the image from importing by adding the following to your theme’s functions.php file:

add_filter( 'tribe_fb_event_img', 'remove_facebook_image' );
function remove_facebook_image() {
return false;
}

Let me know if this helps.

Thanks!

 

[Josh]

Hey Alexander,

Thanks for reaching out to us!

The “Price” field is available when just the Events Calendar (or with just Events Calendar PRO as well). However, when a ticketing solution is added, that feature gets overwritten with the tickets.

You can get the prices added back to the events by adding tickets. If you don’t need the tickets, you can get the Price field back by removing the Tickets plugin.

Let me know if this helps.

Thanks!

[Josh]

Hey Michael,

Thanks for reaching out to us!

It looks like there may be some additional styles to elements there that can be removed or targeted specifically for the calendar. However, without a link to a live (or staging) version where this is being used it’s going to be difficult to provide any more specific help or code snippets to address these issues on your homepage.

If you are able to provide a link that we can look at it will help us to give you a little more feedback on this one.

Thanks!

[Josh]

Hey,

Thanks for reaching out to us!

The issue of multiple events importing via Facebook Importer has been a bit of an elusive one for us. Many times we’re unable to recreate the issues. One thing that would help here though would be if you were able to supply a database dump which includes the duplicated events. If you would like, you can supple links to those as a private reply here or email them to support[at]theeventscalendar.com

Thanks!

[Josh]

Hey Michael,

Thanks for reaching out to us and for bringing this to our attention.

I’ll reach out to our developers to review these results and determine what the next steps should be in addressing any of these validation type errors.

Thanks!

[Josh]

Hey Kate,

Thanks for reaching out to us on this one.

It sounds like you’re experiencing a known bug with localized time conversion. Would you mind trying the following snippet by adding it to your theme’s functions.php file to see if it helps to address the issue?

https://gist.github.com/barryhughes/b376c49b447460b2d122

Let me know if this helps.

Thanks!

[Josh]

Hey Ben,

Thanks for reaching out to us!

I’ll try to answer your questions to the best of my ability! As a general rule for this type of stuff we recommend just purchasing the plugin to see if it fits your needs. We have a 30 day refund policy so if it doesn’t work for you we would be happy to refund your purchase within 30 days of original purchase.

1. The tags should work great the way you’re wanting. My only concern would be the description of hierarchy within your tags. By default tags don’t naturally have that hierarchy. There could potentially be some issues here.
2. Yes, if you select to have the events show up in your main loop, the events should display in those archives.
3. This should work as well. If you’re using the default “Event Categories” they’ll automatically be added to the filter bars. If you’re using a custom taxonomy, you’ll have to do a bit of customization to have that added to the filter bar filters.
4. Yep, the calendar can be controlled with query strings so you can have an event archive based on a category and then include items like “?tribe_event_date=” to go to specific dates. The easiest way to grab these is to just navigate to the screens you’d like to use and pull the strings from the URL.

Let me know if this helps.

Thanks!

[Josh]

Hey,

Thanks for reaching out to us!

I’ve added a Mongolian translation option for Pro. Let me know if you have translations needed for any of the other plugins.

Thanks!

[Josh]

Hey Mad Dog,

I did some further testing on a vanilla WordPress install and the original snippet from the other thread (excluding the additional check for main query added here) seems to work as expected. That check can actually be excluded as long as you aren’t using any other event queries on the page.

Does the original snippet work for you with a search date added?

Thanks!

[Josh]

Hey,

Just wanted to follow up here real quick.

I did some test by rolling back some of the changes to the mobile javascript code to see if I could pinpoint exactly where the issue cropped in. I was able to correct the “Events for…” issue by doing this, however with a default Genesis theme wasn’t able to get the list to display.

Will follow back up after hearing back from one of our devs.

Thanks!

[Josh]

Hey Tommy,

Thanks for reaching out to us!

The “tribe_venue” is a custom post type built using the built-in WordPress function for post types. A couple of options that you do have to create the archive:

1. You can filter the post type args for the venues ( tribe_events_register_venue_type_args ) to include an archive.
2. You could also create a new page template that has a WP_Query to query the “tribe_venue” posts and then create the layout within the template.

Let me know if you have any further questions.

Thanks!

[Josh]

Hey Ben,

Thanks for reaching out to us!

On initial view of those warnings, my first assumption would be that there is a customization that exists (possibly within your theme or another plugin) that is manipulating the cost display of the events. Are you aware of any changes that may have been made in the past in this regard?

If so, you can add those snippets here and we can take a quick look at them to see what the potential conflict could be.

Thanks!

[Josh]

Hey Mark,

Thanks for reaching out to us!

The 4.0.1 update includes the fix for the update issue that existed for Community Events. If there is any concern, the best approach is to do a bulk update by selecting the check box next to each of the available TEC updates and selecting the “Bulk Update” option.

Let me know if this helps.

Thanks!

[Josh]

Hey Matt,

Thanks for following up and providing the screenshots.

I tested by creating a new recurring event with the same settings and then tested visiting each instance and didn’t have any redirection issues for any of those events.

A couple of questions that may help us here:

1. If you try to create a new recurring event with the same settings does the issue occur on the newly created event?
2. Can you follow up with the system information from your site in a private reply? You can find that under the “Help” tab within your Event Settings.

Thanks!

[Josh]

Hey Dan,

To verify, are you using the WooTickets plugin or are you using the new Events Tickets Plus plugin along with WooCommerce. You can learn more about the difference here. We’re still supporting WooTickets, however we’ll no longer be updating the plugin and all the functionality has been moved to the Events Tickets Plus and you should have a free version of the plugin available within your dashboard as a previous purchaser of the WooTickets plugin.

If you would like to continue using the WooTickets plugin you can use a solution like the following to move the form:

if(class_exists('TribeWooTickets')) {
remove_action( 'tribe_events_single_event_after_the_meta', array( TribeWooTickets::get_instance(), 'front_end_tickets_form'), 5 );
}

if(class_exists('TribeWooTickets')) {
add_action( 'tribe_events_single_event_before_the_content', array( TribeWooTickets::get_instance(), 'front_end_tickets_form') );
}

Let me know if this helps.
Thanks!

[Author]

Posts