[Cliff]

Hi, Gowtham. 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. 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, Todd.

Per our Scope of Support / Terms, we wouldn’t be able to help you create a new widget, but I can try to point you in the right direction.

I’d suggest using tribe_get_custom_fields() to get you started.

Please let me know how this goes for you.

[Cliff]

Excellent! Thanks for letting us know.

[Cliff]

You’re welcome to share as much as you want, but a quick overview is probably all we’d mention in the article.

Thanks for whatever you decide to share.

[Cliff]

Hi Erin / Mitch.

Please give this snippet a try:

https://gist.github.com/cliffordp/799c1b546b79ad7626141bdc00974f53

You might need to modify it for your usage, but hopefully it works for you. I didn’t give it 100% thorough testing so please do yourself.

[Cliff]

Hi, Steve. 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:

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. 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. I couldn’t reproduce the issue. I’m glad you got it sorted out. Feel free to share if there’d be any helpful information for other users.

 

[Cliff]

Hi, Jon.

Sorry this issue has been outstanding so long. I can tell you that there’s not a fix scheduled at this very moment. I pinged the development team asking for this to get some priority (i.e. scheduled sooner than any later).

I’ll mark this ticket as Pending Fix, like the other thread you linked to, 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 continued patience.

[Cliff]

Gotcha. Thanks for clarifying.

I’m personally writing this extension’s replacement, which is going to be called PDF Tickets extension.

The PDFs will be saved to your server in the Uploads folder and actual PDF files will attach to ticket emails. The user’s “View your tickets” page (for each event they’re attending) will have the PDF Ticket link if they lost their email.

In other words, there won’t be any more of these view ticket links that require checking credentials. Basically, anyone with the PDF link (in the proper format — it’s not a simple “ticket_1234.pdf” file name) will be able to view/download it.

If all this sounds good to you, I’d guess it’ll be released this or next week.

I’ll mark this ticket as Pending Fix, which means this thread should receive a reply once this new extension has been released.

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

[Cliff]

Hi, Brian. Sometimes bug fixes take longer than we want… sometimes they don’t get scheduled (priority) right away and other times, like in this case, attempting to fix the problem reveals a larger issue.

We do not provide ETAs, but I can guess that it’ll be a decent amount of time longer.

I passed along to the development team that this is an important issue for you.

This thread will get updated once the fix is released.

[Cliff]

Thanks very much for sharing!

Is https://berrywing.com/scan-to-spreadsheet-app/ the one you’re using?

Please do share more about this so we can possibly include it on our KB article for others.

[Cliff]

Hi, Amy. Thanks for the detailed report. I’m glad you got things sorted for now.

Event Aggregator definitely works alongside WooCommerce and many other plugins and themes.

I suggest you 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 (activate WooCommerce again) 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).

Please let me know what you find out.

[Cliff]

This reply is private.

[Cliff]

Hi, Ilkka.

If your event is yoursite.com/event/abc-123/, then are you saying the “View your Tickets” link that goes to yoursite.com/event/abc-123/tickets/ is not working?

Or are you saying that once there (at that /tickets/ URL), that the extension’s view ticket link is not working?

[Cliff]

Hi, Eric.

I just helped someone else with this issue. Please reference https://theeventscalendar.com/support/forums/topic/how-can-i-erase-min-in-the-time-event/ and let me know if going to your WordPress datetime settings was the solution for you too.

[Author]

Posts