[Cliff]

Okay. Thanks for the update. Have a great rest of your week.

[Cliff]

Peggy, I am sorry to hear this isn’t yet resolved for you. However, we do need to isolate the cause of this issue in order to try to further assist you.

Please follow these recommended troubleshooting steps for your own site:

There might be some new updates available. Could you please make sure all your Modern Tribe plugins (and WordPress core) are at their latest versions?

• Downloads / Version Numbers
• License Keys
• TEC Automatic Updates
• or TEC Manual Updates
• WordPress core updates

Once you verify you’re on the latest versions, please test to see if the issue is still happening for you.

If it is, please follow our Testing for Conflicts Guide (basically switch to Twenty Seventeen theme and deactivate all plugins and custom code other than Modern Tribe plugins) and see if that helps narrow down the cause of this.

Of course, we always recommend restorable database and file backups as well as performing modifications first on a staging site before modifying anything on your live/production site.

If it doesn’t, please enable WP_DEBUG and WP_DEBUG_LOG (which will create a file on your server at /wp-content/debug.log if there are any WP_DEBUG messages) and share any debug messages you see while trying to replicate this issue and doing other things on your site relevant to this ticket (such as visiting your site’s home page, events page, single-event pages, and anything else you can think to do).

Then, please share your System Information (while in Testing for Conflicts Mode) in a Private Reply.

That will give me a lot of extra information to help troubleshoot this.

You might also see if you can spot any console errors at your site. (If needed, you may reference our KB article Using Google Chrome Developer Tools.)

Let us know what you find out.

Thanks.

[Cliff]

Glad to hear and thanks for letting us know.

[Cliff]

Ilkka, thanks for your contributions here. However, we need to handle each customer’s situation individually. Therefore, please create your own separate thread and link back to this one.

Stephanie, please reply to my prior message at your convenience.

Thank you both.

[Cliff]

I set it to Private for you.

Sorry you’re experiencing this but since it isn’t currently a confirmed issue so I’d suggest following these recommended troubleshooting steps for your own site:

Please make sure all your Modern Tribe plugins (and WordPress core) are at their latest versions. Then, follow our Testing for Conflicts Guide (basically switch to Twenty Seventeen theme and deactivate all plugins and custom code other than Modern Tribe plugins) and see if that helps narrow down the cause of this.

Please share your System Information (while in Testing for Conflicts Mode) in a Private Reply.

Of course, we always recommend restorable database and file backups as well as performing modifications first on a staging site before modifying anything on your live/production site.

Let us know what you find out.

Thanks.

[Cliff]

Hi, Jessy. Thanks for your interest in our plugin suite.

We do not provide support for any third-party plugins, but if they claim integration with our products then you can contact them to ask such questions.

I found this article in Elementor’s docs: https://docs.elementor.com/article/285-how-to-add-a-calendar-to-elementor

It doesn’t mention support for our plugins. Maybe you’re just asking about using our shortcodes within their page builder?

Our Events Calendar PRO paid add-on does have some shortcodes. If you’re asking about using these within Elementor, please know that we don’t guarantee integration and you’ve posted in the Pre-Sales section of our Help Desk.

If you have Events Calendar PRO, please login to your account and post your question in the appropriate forum: https://theeventscalendar.com/support/forums/forum/events/events-calendar-pro/

Please let me know if you have any follow-up questions on this topic.

[Cliff]

I revisited your link and I see you’re using Event Tickets Plus (ET+) on a recurring event. Unfortunately, ET+ doesn’t currently support PRO’s recurring events.

If you start to create a ticket for a recurring event, there will be a little question mark notice that reads:

Currently, tickets will only show up on the frontend once per full event. For PRO users this means the same ticket will appear across all events in the series. Please configure your events accordingly.

You should add your vote to this existing feature request for Event Tickets to support PRO’s recurring events.

Something some users are doing right now is using PRO’s recurring events to populate their events calendar but then breaking each occurrence from the series to turn them into single events — basically using PRO as an event generator but not actually using its recurring events functionality on the front-end. Others are just dealing with the tickets on recurring events even though you can’t then tell which occurrence they reserved the ticket for… use this information for your own reference but please don’t take it as any sort of recommendation.

All that said, for your specific use case, you might be able to get away with adding a ticket to a recurring event and then add some CSS or PHP to make it not appear on the recurrence instances, only the main/initial instance of the event.

If this sounds like what you would want, please explain why only 1 event is appearing at your link instead of both and I can try to advise from there.

Thank you.

[Cliff]

Hi, Stephanie. Thanks for your detailed report. Sorry you’re experiencing this.

I viewed your System Information Report and see that your WordPress General Settings and PHP/Server time zones are both “America/New_York”

We’ve seen this issue when an event was created during Standard Time for an event occurring during Daylight Savings Time, particularly events in a recurrence series where some occur prior to DST changing.

Are you experiencing this 1) only with recurring events, 2) for newly-created events or just ones you created a few weeks ago (prior to DST changing)?

[Cliff]

I see these messages at the top of that link:

Notice: /wp-content/plugins/the-events-calendar/src/deprecated/TribeEvents.php is deprecated since version 3.10! Use Tribe__Events__Main instead. in /wp-includes/functions.php on line 3967

Notice: wpb_map is deprecated since version 4.2 (will be removed in 6.0)! Use vc_map instead. in /wp-includes/functions.php on line 3839

Notice: wpb_map is deprecated since version 4.2 (will be removed in 6.0)! Use vc_map instead. in /wp-includes/functions.php on line 3839

Notice: wpb_map is deprecated since version 4.2 (will be removed in 6.0)! Use vc_map instead. in /wp-includes/functions.php on line 3839

Notice: wpb_map is deprecated since version 4.2 (will be removed in 6.0)! Use vc_map instead. in /wp-includes/functions.php on line 3839

Notice: wpb_map is deprecated since version 4.2 (will be removed in 6.0)! Use vc_map instead. in /wp-includes/functions.php on line 3839

Notice: wpb_map is deprecated since version 4.2 (will be removed in 6.0)! Use vc_map instead. in /wp-includes/functions.php on line 3839

Notice: wpb_map is deprecated since version 4.2 (will be removed in 6.0)! Use vc_map instead. in /wp-includes/functions.php on line 3839

Notice: wpb_map is deprecated since version 4.2 (will be removed in 6.0)! Use vc_map instead. in /wp-includes/functions.php on line 3839

Notice: wpb_map is deprecated since version 4.2 (will be removed in 6.0)! Use vc_map instead. in /wp-includes/functions.php on line 3839

Notice: wpb_map is deprecated since version 4.2 (will be removed in 6.0)! Use vc_map instead. in /wp-includes/functions.php on line 3839

Notice: wpb_map is deprecated since version 4.2 (will be removed in 6.0)! Use vc_map instead. in /wp-includes/functions.php on line 3839

Notice: wpb_map is deprecated since version 4.2 (will be removed in 6.0)! Use vc_map instead. in /wp-includes/functions.php on line 3839

Notice: wpb_map is deprecated since version 4.2 (will be removed in 6.0)! Use vc_map instead. in /wp-includes/functions.php on line 3839

Notice: wpb_map is deprecated since version 4.2 (will be removed in 6.0)! Use vc_map instead. in /wp-includes/functions.php on line 3839

Notice: Undefined index: return_title in /wp-content/plugins/disclaimer-by-elan42/disclaimer-by-elan42.php on line 19

Notice: Undefined index: return_text in /wp-content/plugins/disclaimer-by-elan42/disclaimer-by-elan42.php on line 19

You have multiple issues going on:

1. This is the only one that relates to our plugin, but it’s an odd one. I’m unsure what could be in use on your site that has this old code in it. I’d recommend checking your theme’s functions.php file for “TribeEvents”.
2. I think this is an issue with Visual Composer. Maybe you have an outdated version bundled with your theme. Maybe you have a VC add-on that’s outdated.
3. disclaimer-by-elan42 plugin has errors that should be reported to the developer if you’re using the latest version of it.

 

[Cliff]

Using Check Payments, not PayPal (since I can’t pay myself), I changed from On Hold to Processing, then I Bulk Changed from Processing to Completed and the Ticket email didn’t get sent at all. Here’s the video: https://cl.ly/1F3T0d0y2b3b

This isn’t the exact same issue as you’re reporting, but I’ve logged the one I was able to produce.

If you’re able to reproduce your issue with just the minimal plugins and Twenty Seventeen theme and PayPal payment, then we’ll log that as well. If not, then keep troubleshooting after switching to your theme and after re-activating other plugins, especially WooCommerce-related ones.

Please let me know what you find out.

[Cliff]

This reply is private.

[Cliff]

It comes from https://github.com/moderntribe/tribe-common/blob/4.7.9/src/Tribe/Main.php#L188, but I’m unsure if fully/always dequeuing it would cause problems because there are quite a few scripts with “datatables” in their handle…

I’m unsure how I can be of more assistance here. https://wordpress.org/plugins/debug-bar/ and https://wordpress.org/plugins/debug-bar-list-dependencies/ can be really helpful for detecting which scripts are loading.

[Cliff]

We do have a known issue with importing to Outlook because Outlook has a custom set of time zones.

We have plans to implement https://github.com/sabre-io/vobject to support Outlook — and, if appropriate, add a 3rd export button specific to Outlook Export.

I have set this thread to be updated once this solution is available.

[Cliff]

There is a filter to turn on including the event date. Please give this a try:

add_filter( 'tribe_tickets_email_include_event_date', '__return_true' );

Please reference https://theeventscalendar.com/knowledgebase/implementing-custom-code-snippets/ for how to implement custom code snippets.

Please let me know how this goes for you.

[Cliff]

Glad to hear and thanks for letting us know.

[Author]

Posts