[Cliff]

This reply is private.

[Cliff]

This reply is private.

[Cliff]

This reply is private.

[Cliff]

Dan, I figured it out on my testing site. Somehow the Eventbrite API credentials got wiped out and the API connection was reset.

Could you please make sure your API connection is all setup?

• Activate The Events Calendar and Eventbrite Tickets
• Make sure you added a valid license key for Eventbrite Tickets (via Events > Settings > Licenses)
• Enter your Eventbrite application to connect to your Eventbrite account (via Events > Settings > APIs)
  • Make sure to click the Authorization button after entering your API connection keys.
• Look for the Eventbrite import options in the Import and Legacy Import screens
• And/or, look for the Eventbrite options in the wp-admin event edit screen (should work for both new and existing events)

For more details, please reference https://theeventscalendar.com/knowledgebase/new-user-primer-eventbrite-tickets/

Please let me know how this goes for you.

If it does get things working for you, then I’m happy to tell you that I already filed a different bug report to display a wp-admin notice whenever Eventbrite Tickets is active but there isn’t an active API connection (for whatever reason).

[Cliff]

Hi, Kevin. Thanks for your detailed question.

This is a known issue caused by our plugin forcing all events to UTC+0 datetime format. It’s technically the correct time, but Google wants the JSON-LD to be in the event’s local UTC time offset, not converted to UTC+0, which can make things appear to be on a different day but really not.

I’ll 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.

[Cliff]

Hi, John. Sorry you’re experiencing this.

This isn’t currently a known issue so I’d suggest following 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 before modifying anything on your 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. Please also send a screen capture video or an annotated screenshot to demonstrate the issue. 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]

Hi. Sorry you’re experiencing this.

I wasn’t able to reproduce the issue using Chrome’s responsive/device emulator for Nexus 5, but it appears your theme or another plugin is implementing custom scrolling (what’s sometimes referred to as “scrolljacking”)

Therefore, since this likely isn’t an issue caused by our plugin (since we don’t implement any custom scrolling), I’d suggest switching to a WordPress default theme like Twenty Fifteen, Twenty Sixteen, Twenty Seventeen, etc. and see if the issue is no longer there. If this is the case, I’d recommend asking your theme developer about this issue.

[Cliff]

Hi, Anna.

You should change the Nov 7 at 9pm date to Sept 19 at 9pm (a single day from 7-9pm) and then set your recurrence pattern based on that (probably leave the date as it is now).

Please let me know how this goes for you.

[Cliff]

Hi, John.

I appreciate your question and the desire to customize it for your use, but we do not provide customizations, per our Scope of Support / Terms.

It sounds like you might have an existing custom code snippet in place already that you’re looking to tweak a bit. Is this correct? If yes, please share that entire snippet so we could take a look, as well as an annotated screenshot demonstrating what you have now and what you’d like it to be, along with a link to view this in action at your site.

Whether for now or in the future, I’ll also share our documentation and list of known customizers.

[Cliff]

Hi, Yuki.

I looked through our internal bug log and found just one regarding ACF:

wp-admin event edit screen > ACF Pro (Advanced Custom Fields Pro) time picker field breaks:

• Install and activate ACF Pro
• Go to Custom Fields > Add New and create a new field group with a Time Picker in it.
• Set the field group location to “Post Type is equal to Event” like this > https://cloudup.com/cAD4TTbyXlf
• Save the group field
• Go to add or edit an event and you will find the time picker field from ACF breaks.

Is this known issue exactly what you’re experiencing?

It was logged several months ago so if it’s not, please let me know. Additionally, 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.

[Cliff]

Hi, Stephen. Thanks for the helpful screenshot.

I was able to reproduce this on my own iOS device, but I’m not sure it’s something we’d consider “fixing” because it actually is a text field. The datepicker makes it significantly easier to insert a valid date (text) format, and it works after tapping “Done” to dismiss the keyboard.

I didn’t test on Android, but this article might be helpful if you want to customize how this text field works on your own site: https://stackoverflow.com/questions/15135784/how-to-disable-keyboard-appearing-when-hitting-on-a-text-field-ios (third-party, not guaranteed or supported by us)

To implement something like that, you might need to follow our Themer’s Guide to customize /wp-content/plugins/the-events-calendar/src/views/modules/bar.php

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

[Cliff]

Hi, Dan.

This is odd, but I was able to reproduce the issue on my own testing site as well.

I’ll 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.

[Cliff]

Hi, Stephane.

I believe you’re requesting the same thing as one of our existing feature requests: https://tribe.uservoice.com/forums/195723-feature-ideas/suggestions/18537427-qr-code-multiple-use-for-attendance

Please do add your vote there.

This allows us to gauge interest in this particular feature request, which helps us prioritize our development efforts.

One idea is that you could create Ticket A and say it’s $20 and then Ticket B and say it’s $0… both on the same event.

Then, hide Ticket B from view on the event page, like via CSS, but use a snippet like the one below to force adding Ticket B to the cart whenever Ticket A is added:

https://gist.github.com/cliffordp/30481ca323012e298418095476d49337

The snippet would need a little bit of tweaking in order to work for your specific setup — and would need to be different per each multi-day event — but it might be a help in the right direction.

Another simpler idea would be to just create 2 tickets and spread the cost between the 2 days, like Ticket A for $10 and Ticket B for $10 and hope that they figure it out.

Whatever you try, please let me know what worked for you and what didn’t.

[Cliff]

This reply is private.

[Cliff]

Hi, Nicolas. Just checking in on this one. Please let me know how things went for you.

[Author]

Posts