[Cliff]

Thanks so much. Have a great week!

[Cliff]

Hi, Karen.

Thanks for your detailed question.

Community Tickets currently utilizes PayPal’s Split Payments functionality. Each of your site users who wants to create events that sell tickets (all done via the Community Events form) must first enter their PayPal email address.

Here’s a code snippet that puts such a notice above the Community Events form:

https://gist.github.com/cliffordp/6250485f5fe850e5404059c48de3e3ed

You may also want to look through our existing feature requests for Community Tickets.

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

[Cliff]

Hi, John. Thanks for troubleshooting this.

Please reference our Themer’s Guide and then copy /wp-content/plugins/the-events-calendar/src/views/single-event.php to [your-child-theme]/tribe-events/single-event.php and then comment out or fully delete Line 58:

echo tribe_event_featured_image( $event_id, 'full', false );

Please let me know if that removes the featured image from your Single Event view.

[Cliff]

Hi, Kimberly.

I was able to reproduce this issue for venues that have a title but no address/location information.

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]

Ken, here’s a video answering a couple of your questions: https://cl.ly/2Q2t0N0f2M0w

Here’s a code snippet for moving things around:

https://gist.github.com/cliffordp/f95b520a71635fd4e9d73eb2af73bd5e

You could reference it for your own customization to only display it for logged in users or however else you want to handle things.

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

[Cliff]

Hi, David.

If I’m understanding you correctly, you want Attendee Meta information collected with each ticket (e.g. Name & Email Address)… but you don’t???

Please explain exactly how you’d like this to work.

Thank you.

[Cliff]

Hi, Bryan. Sorry you’re experiencing this.

This isn’t currently a known issue, and I wasn’t able to recreate it on Events Categories pages, 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 Sixteen theme and deactivate all plugins and custom code other than Modern Tribe plugins) and see if that helps narrow down the cause of this.

If it doesn’t, please enable WP_DEBUG and WP_DEBUG_LOG and share any debug messages you see while changing tickets quantity, navigating your site’s home page, events page, single-event pages, and any other of your site’s pages relevant to this ticket.

Then, please share your System Information (while in Testing for Conflicts Mode). That will give me a lot of extra information to help diagnose the problem.

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]

This reply is private.

[Cliff]

Please provide a link to an event that is experiencing this? I wonder if it’s because there are very many Attendee Meta fields. If there are, maybe try removing all but 5 of the Attendee Meta fields for this event and see if it then works.

Thank you.

[Cliff]

That setting does not go to zero, but you can set it to 1.

If it’s seemingly not taking effect, it could be because the events were created in a previous version.

If they’re really a bother, you could use Advanced Post Manager to find them and delete them manually.

Then see if after a month the newly-created events are working for you.

Sorry for the trouble. Let me know how it goes for you.

[Cliff]

Thanks for all those details.

I was able to reproduce the issue and filed the bug to be fixed soon.

In this file: /wp-content/plugins/events-calendar-pro/src/Tribe/Asset/Ajax_Maps.php

For me, replacing
wp_register_script( ‘tribe-gmaps’, $url, array( ‘tribe-events-pro’ ) );
with
wp_register_script( ‘tribe-gmaps’, $url );

resolves the issue in WordPress Query Monitor, but I have no idea what ‘tribe-events-pro’ script is or was or should be.

However, our developers will figure it out for a near-term plugin update.

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]

Thanks for that information.

I’ve asked that third user for their system information report as well.

Your debug log is more detailed than normal, so I’m guessing you have some sort of logging enabled, which is no problem at all 🙂

Anyway, I saw messages from your SumoMe and Jetpack plugins. I’d suggest making sure those plugins are at their latest versions and, if they are and the debug messages are still appearing, passing those errors onto the respective plugin support teams.

I also saw “The post type shop_subscription is not registered” and other similar messages as if you had WooCommerce Subscriptions active but now do not — or possibly a similar situation.

And I visited your testing site and saw a console error at your site about not having your Google Maps API Key installed. I’d recommend resolving that too, especially for a production site, but it shouldn’t be having an effect on this issue–just a general suggestion.
(If needed, you may reference our KB article Using Google Chrome Developer Tools.)

I also saw very many Attendee Meta fields at your testing site. Is the issue that the fields are not displaying for you when the ticket quantity changes from 0 to 1 — or is it that the data is not coming through to the Attendees Report?

If the latter, please try changing the Attendee Meta fields from the 28 fields you have now to something smaller, like 5 fields, and see if the Attendee Meta data then does come through to the Attendees Report.

Thanks!

[Cliff]

Hi, David. Sorry you’re experiencing this.

There are 2 other users who have reported this:

• https://theeventscalendar.com/support/forums/topic/no-attendee-info-wp-v4-7-1/
• https://theeventscalendar.com/support/forums/topic/attendee-details-are-not-saving/

However, I haven’t been able to reproduce this with RSVP or WooCommerce ticket types.

Please share your System Information. That will give me a lot of extra information to help diagnose the problem.

[Cliff]

Single events do have post IDs, but you could target all of them via body.single-tribe_events

Please let me know how this goes for you.

[Cliff]

If I understood your reply correctly, you’re wondering why the reCAPTCHA is not displaying for logged-in users.

This is the way Community Events has always worked.

However, if you want to force the reCAPTCHA to display for all users, including logged-in users, you this snippet should work for you:

https://gist.github.com/cliffordp/9fc77333d8523ecf180b382ee86311a5

Please let me know how this goes for you.

[Author]

Posts