[Cliff]

This reply is private.

[Cliff]

Did you purchase a ticket with a unique Attendee Information value and search for it in your database?

Please use the Duplicator plugin to create a full backup (files and database — please check the box to exclude the uploads folder if it’s large) and link me to download it in a Private Reply.

I might then be able to try and replicate the issue on my own testing server with your site’s files and database.

Thank you.

[Cliff]

This reply is private.

[Cliff]

This reply is private.

[Cliff]

On your testing site, please go to wp-admin > Events > Settings > Tickets and make sure you have boxes checked for the 2 options in the “WooCommerce Support” section.

After saving these options, please try again. If still not, please re-share your testing site’s System Information Report in a Private Reply.

[Cliff]

This reply is private.

[Cliff]

Math, I’m very sorry to hear this still isn’t working for you.

Let’s try this: install the Duplicator plugin and create a full backup (files and database — although you can exclude your uploads folder if it’s huge) and I can see if I can troubleshoot this for you on my localhost copy of your site… if you’re interested of course.

If you do want me to try this for you, please provide a download link in a Private Reply.

[Cliff]

Hi, Kevin. Sorry you’re experiencing this.

I haven’t seen this reported by others, and I wasn’t able to reproduce the issue on my own testing site.

Please delete The Events Calendar and Events Calendar PRO plugins and install fresh versions from the wp-admin plugin installer after downloading the latest versions from https://theeventscalendar.com/my-account/downloads/

Deleting The Events Calendar or its add-on plugins will NOT delete any of your data if you delete it via the WordPress plugin manager because that’s how we’ve decided to code our plugin.

FYI: deleting any plugin via FTP or cPanel’s File Manager (i.e. deleting just the files from the server) will also ensure a plugin gets deleted (if you delete the entire plugin folder) without removing any data from the database. This can sometimes be helpful to know in cases where a plugin does run an uninstall routine to delete data (again, our plugins do not run such a routine at this time and probably never will).

You can also see the difference when you click to delete a plugin, like this.

[Cliff]

Hi again, Huiwen.

They can enter it at your-site-com/events/community/payment-options

The data is stored in the wp_usermeta database table under the tribe_events_community_tickets meta_key, but it’s in a serialized array so it really shouldn’t be modified (input, edited, or deleted) via the database.

You could use a plugin like https://wordpress.org/plugins/user-switching/ (third-party, not guaranteed or supported by us) if you already know which PayPal email address belongs to each of your users.

Please try this snippet (or use it as a starting point).

Please let me know all this goes for you.

[Cliff]

Hi, Sagi. Sorry you’re experiencing this.

Please remove the license key from your site’s wp-admin > Events > Settings > Licenses tab

Then visit https://theeventscalendar.com/license-keys/ and remove your site from being assigned that license.

Then, re-enter that license key at your site’s wp-admin > Events > Settings > Licenses tab

Please let me know how this works for you.

Thanks!

[Cliff]

Neil, sorry this has taken so long to get released.

We do want to release recurring tickets functionality, but the underlying infrastructure of how recurring events are created in the database and how tickets are applied to them does not support it. We’ve been making quite a few incremental changes over the past year and are continuing to do so. It’ll make our solution more robust/flexible and one of those benefits is the ability to support tickets for recurring events.

That said, here’s our current info about it:

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.

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

[Cliff]

tribe_get_events() uses getEvents() which runs WP_Query with the passed $args… so maybe keep those in there and give it a shot?

References:

• https://github.com/moderntribe/the-events-calendar/blob/4.5.1/src/functions/template-tags/general.php#L183-L219
• https://github.com/moderntribe/the-events-calendar/blob/4.5.1/src/Tribe/Query.php#L1017

Please let me know how this goes for you.

[Cliff]

Unable to test on local environment due to the licence to domain.

Please reference https://theeventscalendar.com/knowledgebase/using-one-license-live-dev-sites/

Even if you are seeing notices of license out of installs on your localhost copy, the plugin will still work; it just won’t be able to get automatic updates installed.

So, yes, you can still test this on your localhost, and I recommend you do.

I’d also suggest resolving those WP_DEBUG messages on localhost and then pushing the changes to production once you determine the cause of them. It looks like you’ll need to fix issues with:

• Visual Composer / WP Bakery map (2 notices)
• your theme’s functions.php file ($target variable on line 563)
• your theme’s functions.php file ($sub_heading variable on line 675)

And, of course, we recommend you use the latest template files.

The main thing you’ll need to do for us to continue helping you debug is follow our Testing for Conflicts Guide. It’s your choice whether that’s on your live site (obviously not the best practices) or on a staging/development/localhost copy (recommended).

[Cliff]

I’m sorry, but there are a few things here that are causing me not to be able to really help with this:

• It’s not in English so I can’t tell what each of those texts are to point me to a guess of where it might be coming from in the code.
• You’re on localhost so I can’t use the browser inspector to know what you’re referring to via page source.
• Your screenshots don’t look like normal display. In other words, I think your theme may be at play here because I don’t see a similar layout/display when using a WordPress default theme like Twenty Fifteen, Twenty Sixteen, Twenty Seventeen, etc.
• Finally, we cannot provide in-depth customization help, per our Scope of Support / Terms.

If there’s a code snippet you’d like me to put some eyes on or something else I can help you with, please update this ticket or create a new ticket if it’s a separate issue.

Thank you very much for your understanding.

If you need some coding help, you may want to ask your developer or reference our documentation and list of known customizers.

[Cliff]

Thank you. I’ll document each event I tested:

1)

If we download the basic.ics file you initially shared, here’s the code for one of the events in question:

BEGIN:VEVENT
DTSTART:20170501T233000Z
DTEND:20170502T013000Z
DTSTAMP:20170519T104656Z
UID:[email protected]
CREATED:20170210T220426Z
DESCRIPTION:
LAST-MODIFIED:20170428T150005Z
LOCATION:Fowler Middle School\, 10865 SW Walnut St\, Tigard\, OR 97223\, US
A
SEQUENCE:1
STATUS:CONFIRMED
SUMMARY:Girls Tennis vs Blanchet Catholic
TRANSP:OPAQUE
END:VEVENT
BEGIN:VEVENT
DTSTART:20170428T233000Z
DTEND:20170429T013000Z
DTSTAMP:20170519T104656Z
UID:[email protected]
CREATED:20170210T220249Z
DESCRIPTION:
LAST-MODIFIED:20170425T160143Z
LOCATION:Fowler Middle School\, 10865 SW Walnut St\, Tigard\, OR 97223\, US
A
SEQUENCE:1
STATUS:CONFIRMED
SUMMARY:Girls Tennis vs Valley Catholic
TRANSP:OPAQUE
END:VEVENT

The “Z” at the end of the datetimes means they are in UTC timezone. Therefore:

DTSTART:20170428T233000Z
DTEND:20170429T013000Z

Would be 11:30 pm April 28 – 1:30 am April 29 UTC.

In LA timezone, which is UTC-7 during Daylight Savings Time (DST), this would be 4:30 pm – 6:30 pm April 28 UTC-7

Therefore, your screenshot shows it imported the start time correctly as 4:30pm L.A. time.

I imported this event on my own testing site:

• Preview: https://cl.ly/1K430c1S2l0y
• Actual import: https://cl.ly/3M4131031l0x

Obviously, the date imported incorrectly, but the times imported correctly.

2)

BEGIN:VEVENT
DTSTART:20170501T230000Z
DTEND:20170502T020000Z
DTSTAMP:20170519T113049Z
UID:[email protected]
CREATED:20170428T201525Z
DESCRIPTION:
LAST-MODIFIED:20170428T201525Z
LOCATION:Meriwether National Golf Club\, 5200 SW Rood Bridge Rd\, Hillsboro
\, OR 97123\, USA
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:JV Golf Tournament
TRANSP:OPAQUE
END:VEVENT

From that:

DTSTART:20170501T230000Z
DTEND:20170502T020000Z

This event is:

• UTC: 11pm May 1 – 2 am May 2
• UTC-7: 4pm – 7pm May 1

My testing:

• Preview: https://cl.ly/2h0y0X3d3642 (correct)
• Actual: https://cl.ly/3d2I0A3B0337 (also correct)

===

Ultimately, I think there is a bug here, possibly two.

I’ve shared this testing with our developers and will mark this ticket as Pending Fix, which means this thread should receive a reply once the applicable fix has been released. I cannot guarantee when it will be fixed as it’s in the development team’s hands now. They need to assign it, code it, test it, and schedule it for release.

I apologize for this issue and appreciate your understanding and patience.

[Author]

Posts