[Josh]

Hello shinytiger,

Thanks for following up with us!

Definitely a strange issue. Let me know if the settings you’ve adjusted make a difference.

To test for a conflict, you could try creating another install with your hosting provider as a subdomain of your current site. You could then start with a blank slate and start adding the plugins and themes 1 by 1 over to see if one of the plugins or the them is the culprit.

I apologize for the inconvenience this issue has caused. Let me know how the previous adjustments work for you.

Thanks!

[Josh]

Hello Kyle,

No problem! Glad that was able to help.

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]

Hello bwcberlin,

Thanks for following up with us!

This is definitely odd. Would it be possible to get a link to the test site that you’re using where this is occurring with the default theme and plugins deactivated?

Thanks!

[Josh]

Hey!

I’ve noticed you’ve marked the previous response as the correct answer. I’ll go ahead and close out this ticket but if you have any further questions, please don’t hesitate to open a new one.

Thanks!

[Josh]

Hello albertabrantes,

Thanks for following up with us! I’m glad you’ve got a direction to look to help in resolving your issue.

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]

Hello fortgordonmwr,

Thanks for following up with us!

I’m sorry the shortcode solution didn’t work for you. One other thing to try would be to add the “tribe_is_event_query” conditional to the initial snippet that you’re using. This should ensure that function only runs when the main loop of the page is and event display. As long as the widget you’re using isn’t on an event page, it shouldn’t be affected by the original exclusion of the category.

Let me know if this helps.

Thanks!

[Josh]

Hello gilcatt,

Thanks for following up! I’m glad the suggestion seems like it could be a good solution.

Unfortunately I’m not able to go into exact detail here in support because that would actually require several hours of custom development and testing to get a good solutions and provide those details.

However, to be more specific as to where I would start looking at development, I would:

1. Look at creating a function that fires when a product is created.
2. I would first check to see if the product had variations for dates.
3. If so, I would run wp_insert_post for each date variation.
4. The two variables you’ll definitely need for each ‘wp_insert_post’ are ‘post_title’ (I would make this a string that combines the product name and date) and ‘post_type’ (tribe_events).
5. You would then need to grab the dates and assign those with the new event (great resource)

Hopefully this helps to get you pointed in the right direction.

To address the shortcode issue again, I just tested purchasing a product via the shortcode I placed on an event and was able to complete the transaction. It sounds like this still may be a plugin conflict or possibly a different setting within WooCommerce that may be causing the issue. Have you tried your existing configuration with default WooCommerce settings, no other plugins, and a default theme? If that works, you can start to reconfigure as needed to find where the conflict is occurring.

I’m sorry I wasn’t able to give you a direct response however I hope this was able to point you in the right direction.

Thanks!

[Josh]

Hello gilcatt,

Thanks for following up with us and providing with detailed information about what you’re trying to accomplish! This definitely helpful.

As a start, I’ll address the concern about the shortcodes being used within the event descriptions. I tested this out within my local install with a fresh version of WooCommerce and WooCommerce Tickets plugin and was able to get the ticket to display ( using this shortcode https://cloudup.com/cRHtFlCv5HN, I was able to display https://cloudup.com/cNV01woBRH1). When you’re adding the shortcode, are you using the main product ID or are you using the ID for a specific variation? Also, there could be some other settings associated with the product that may be causing it not to display. When you use the shortcode, is the area showing blank or is it outputting the raw shortcode?

To address the general issue of what you’re trying to accomplish, it sounds like you may not need the WooCommerce tickets plugin. I may be mistaken, but it sounds like a good approach from a usability perspective would be creating the sessions as products in WooCommerce and then setting the different dates as product variations or attributes (I’m not as familiar with the implications between these two options within WooCommerce) for that product. Then, when a new product is created with date variations, you can have a function run which automatically creates new events within the “tribe_events” CPT using “wp_insert_post“.

With this approach, you could have all the details for the event (date, time, title, and even the appropriate shortcode to output the product onto the event content area) automatically added when the new “session” product is created.

Unfortunately I’m unable to dig too deep into this particular aspect here within the support forums but hopefully this would be enough to get you pointed in the right direction if this sounds like something that may be useful to you.

Thanks!

[Josh]

Hello,

This is an issue that is on our radar and we’re looking into the options for resolving this within our core plugin within an upcoming release. I apologize for any inconvenience this may cause in the meantime.

As progress is made, you’ll be notified via this thread when the update will be available 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]

Hello rayela,

Thanks for following up with us!

Unfortunately I’m unable to replicate the javascript error mentioned above with my local install using the latest version of the plugin as well as multiple default themes and other custom themes.

As I mentioned previously, our plugin relies heavily on the use of AJAX . Unfortunately this can, on occasion, cause some conflicts with themes that also rely heavily on AJAX. Themes can be made to be compatible with our use of AJAX but that would require custom development beyond what we’re able to provide via our support forums.

I apologize for the inconvenience. I definitely understand the frustration that comes along with incompatibility issues such as these.

Thanks!

[Josh]

Hello bluebeesocial,

Thanks for reaching out to us!

This is definitely a strange issue to be having. When adding the prices for the event, did you add the price in the Eventbrite “cost” field (https://cloudup.com/cGaSSP7ZPSU) for each ticket or were prices set in the default “cost” field (https://cloudup.com/clty4pHVxSh) prior to adding the Eventbrite plugin?

Thanks!

[Josh]

Hello wkerslake,

Thanks for reaching out to us!

This definitely sounds like a strange issue to be having. Would you be able to send over screenshots of the issues you’re noting. I’ve looked on my local install however based on the description I’m not seeing the same issues you’re noting.

A couple of quick questions to see if we can help to find the root of the problem:

1. <span style=”line-height: 13px;”>Are you using a translation file translating the strings into another language in your install? It may be that the translation file has an error and is putting out empty strings. </span>
2. Have you tried following our Testing for Conflicts procedures to see if this is due to a plugin or theme conflict?

I’m sorry I wasn’t able to give you a direct response however I hope this was able to point you in the right direction.

Thanks!

[Josh]

Hello glennpackham,

Thanks for reaching out to us! This is actually a bug that we’re aware of and will be looking to correct in an upcoming release. I’ve added this thread to our internal tracking system. You’ll be notified as we make progress on this issue and when the fix will be released.

I’m sorry for the inconvenience.

Thanks!

[Josh]

Hello masteagall,

Thanks for reaching out to us!

I apologize for the inconvenience in using our plugin as well as trying to navigate the documentation through our site. We working on new site for The Events Calendar that will have a much stronger focus on search as well as updated tutorials. A detailed tutorial about “tribe_get_events” would definitely be a very valuable tutorial for us to invest in.

I actually did a little research and it looks like you can use  ” ‘tribeHideRecurrence’ => 1 ” as an arg for tribe_get_events to hide multiple instances of recurring events.

Let me know if this helps.

Thanks!

[Josh]

Hello cjoles,

In regards to the first part of the post, I believe the previous response to your other thread still be the starting point in the conversation with Bluehost.

With the photos, are they showing up under the wrong event or are they not showing up on events at all?

Thanks!

[Author]

Posts