[Josh]

Hey!

Thanks for reaching out to us!

This is actually a known bug that we have a fix for coming in our upcoming maintenance release. In the meantime, you can get the styles corrected for the Event List widget by adding thefollowing snippet to your theme’s functions.php file.

https://gist.github.com/jesseeproductions/9ac665ddcdef95c8a2e5

Let me know if this helps.

Thanks!

• This reply was modified 11 years, 4 months ago by Josh.
• This reply was modified 11 years, 4 months ago by Josh.

[Josh]

Hey Marc,

Thanks for reaching out to us! I made a couple of quick modifications to the snippet you provided. I haven’t tested it but it should be enough to help you get the customization you’re looking for live.

add_filter( 'tribe_event_featured_image', 'set_default_featured_img', 10, 4 );

function set_default_featured_img( $featured_image, $post_id, $size, $image_src ) {
if ( ! $featured_image ) {
$post_id = tribe_get_organizer_id();
$image_src = wp_get_attachment_image_src( $post_thumbnail_id ( $post_id ), $size );
return $image_src;
} else {
return $featured_image;
}

Let me know if this helps.

Thanks!

[Josh]

Hey,

Thanks for reaching out to us!

The simplest way to share screenshots may be to share them via dropbox or similar storage type site. I tested the tickets on a local install and inventory counts appeared to be working properly based on the limits I set.

As an initial step, have you tried following the Testing for Conflicts procedures to ensure there isn’t a conflict somewhere that may be causing the issue?

Let me know if this helps.

Thanks!

[Josh]

Hey,

Thanks for reaching out to us!

The simplest way to share screenshots may be to share them via dropbox or similar storage type site. I tested the tickets on a local install and inventory counts appeared to be working properly based on the limits I set.

As an initial step, have you tried following the Testing for Conflicts procedures to ensure there isn’t a conflict somewhere that may be causing the issue?

Let me know if this helps.

Thanks!

[Josh]

Hey Peter,

Thanks for reaching out to us!

It looks like the extra output is the date that gets pulled in as the first part of the event. It looks strange on your site since there is custom styling for this widget that doesn’t include this element. The simplest way to remove it would be to add the following to your child theme’s stylesheet:

.tribe-mini-calendar-event .list-date {
display: none;
}

Let me know if this helps.

Thanks!

[Josh]

Hey Greg,

Thanks for reaching out to us! Looks like you’re from a very beautiful part of Georgia! My wife and I have been talking about moving up toward the Jasper/Ellijay area for a couple of months now.

I apologize for the issues you’re having with using our plugin. Hopefully we can get the sorted out for you quickly.

Looking at your site I wasn’t able to see any instances of html code being output into an event, if this is still an issue can you send me a link to an event with the html being output?

Overall, it looks like all of the information associated with the WooCommerce Tickets plugin is missing from the page. There are a couple of things that may be causing the issue:

1. Can you verify that the WooCommerce Tickets plugin is still activated on the site? If so, can you verify that it is also at the same version of the plugin as The Events Calendar (latest version is 3.9).
2. Have you tested with a default WordPress theme? There could be some old template files within a “tribe-events” folder of your theme that may not have the necessary hooks for the ticket information to be hooked to.
3. Ensure that there isn’t a sale start and end date on the tickets. If there is, and the start date hasn’t come, the ticket information won’t display on the event page.
4. Finally, you mentioned that you deactivated some plugins and switched themes, can you verify that you’ve followed the complete Testing for Conflicts procedures to ensure there isn’t a conflict at the root of the issue.

I apologize again for the issues you’re experiencing. Hopefully these suggestions will help to get you pointed in the right direction. Let me know if this helps.

Thanks!

[Josh]

Hey Marta,

Thanks for reaching out to us!

I apologize for the issues you’re facing in using our plugins. All of our translations are community driven, unfortunately it sounds like this particular translation may still be in need of an update. If you would like, check out this thread from the Translations forum. It’ll help in figuring out how to apply translation for these strings as well as give you the opportunity to update the Catalan translation.

I apologize again for the inconvenience. Let me know if this helps.

Thanks!

[Josh]

Hey!

Thanks for reaching out to us!

I’m glad you were able to find what you were looking for! Sonya, you can find that file at wootickets > views > wootickets > tickets.php. 

However, was there a technical reason you weren’t able to follow the Themer’s Guide to move that file into your theme to make the customization? This will ensure that it isn’t lost the next time you update the plugin.

Thanks!

[Josh]

Hey,

Just following up! Spoke with one of our developers and it looks like this is something that we can address.

I’ve created the bug report for the issue. You’ll be notified here as we make progress and when an update is ready for release. I’ll go ahead and close this ticket. If you have any further questions please don’t hesitate to open a new one.

Thanks!

[Josh]

Hey David,

Thanks for following up with us!

Is this still an issue? I looked at the site and clicked “find out more” to go to a single-event page and it worked fine. The single event also appeared to display as expected with tickets, content and meta.

Thanks!

[Josh]

Hey Daniel,

I’m glad you were able to get it working! I’ll go ahead and close this ticket. If you have any further questions please don’t hesitate to open a new one.

Thanks!

[Josh]

Hey Nancie,

Thanks for following up with us.

It looks like this is a part of a WooCommerce template. You’ll notice that the first line includes “$args”. This is a variable that gets defined previously. When it is defined, it should be defined with an array and within the array is an argument for “post_type”. That is where you will add the “tribe_events”.

However, the file you’ve pulled this excerpt from may not include the code where the variable is defined. It looks like this may be within a loop template that gets called into another file. You may have to trace back and find the file that this feeds into to modify the variable.

Let me know if this helps.

Thanks!

[Josh]

Hey Felix,

No problem.

We are too! It’s been on our radar for a little while and we’re excited to see it come alive. I’ll go ahead and close this ticket. If you have any further questions please don’t hesitate to open a new one.

Thanks!

[Josh]

Hey,

No problem.

You could fix this issue by taking a slightly different approach to filtering out the events of that category. You could use “pre_get_posts” to modify the loop for the widget. Then, within the query args you could exclude that category using a “tax_query“.

This would remove the category as well as keep those posts from contributing to the count of events returned by the query.

Let me know if this helps.

Thanks!

[Josh]

Hey Felix,

Thanks for reaching out to us!

You’re correct, the WooCommerce Tickets plugin doesn’t currently work with the Recurring Events feature available within The Events Calendar Pro. However, we are in active development of this feature and tentatively have it scheduled for the next release. So, barring any technical difficulties in implementation, the feature should be available within the next couple of months.

As far as other technologies and gateways, our plugin works within WooCommerce. The tickets are essentially WooCommerce Products and the transactions will subsequently be handled completely by WooCommerce. So, if you have an existing plugin or system that works with WooCommerce, it should work perfectly fine when using our plugin.

I hope this helps. Let me know if you have any further questions when considering the transition to our plugin.

Thanks!

[Author]

Posts