[Cliff]

Give this a shot, Kari/Dan:

https://gist.github.com/cliffordp/1b8c808efa4256ebcef2d8805f069595

Please let me know how this goes for you.

[Cliff]

Hi, Gerald. Closing this one in favor of keeping the conversation at https://theeventscalendar.com/support/forums/topic/attendee-information-not-showing-up/

[Cliff]

Carsten, thanks for your thorough reply.

I spoke with our developers and it seems the preferable route here would be to use the filter to just make the taxonomy essentially in existence but not usable/visible.

This is because the taxonomy_exists() check would likely be needed in more than just this location throughout all our plugins, and we don’t have other users asking to implement the ability to remove the taxonomy.

Please share your thoughts on this.

Thank you.

[Cliff]

Cath, providing site-specific CSS fixes isn’t part of our Scope of Support / Terms, but we do try to help where we can from time-to-time.

In my testing, the CSS I provided worked fine, but if it doesn’t for you then you’ll need to figure it out or ask a developer.

Or maybe you’ll need to clear your site’s cache to get the rules you added to go into effect.

[Cliff]

This reply is private.

[Cliff]

Sorry for any confusion, Gerald. It was more of a general recommendation, not suggesting any specific plugin in particular.

It sounds like you’ve dealt with this quite a few times. I hope you can understand that it’d be difficult for me to know which of your many plugins are causing the issue, especially since you’ve been experiencing this multiple times.

Typically, you should develop a new version of your site on a testing/staging/development version of your site and then push to your live server once it’s ready. This is how you can have a site where it runs your “old” site live and then your development site can run the “new” version with our plugins.

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

[Cliff]

Hi, Uwe. Great stuff!

The only thing we have built already for you is https://theeventscalendar.com/knowledgebase/listing-venues-and-organizers/

However, in addition to that, you might like to count the posts per author or possibly change the Organizer post type to be public and support other things that would make it publicly queryable. For this, you’d want to leverage thetribe_events_register_organizer_type_args filter and reference register_post_type()

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

[Cliff]

Hi, A.

It seems your site already has some customizations in place, but here’s the information how to get started with customizations: Themer’s Guide

If you have something more specific you get stuck on, please let me know

Please note that threads get Closed automatically after a couple weeks of inactivity. If it does get Closed, please open a new thread, adding your current problem description and also linking back to this thread.

Thank you!

[Cliff]

This reply is private.

[Cliff]

Hi, Carsten.

You might want to reference a snippet like this: http://w4dev.com/wp/unregister-wordpress-taxonomy — except use Tribe__Events__Main::TAXONOMY in place of ‘taxonomy_to_remove’

Additionally/Alternatively, you may want to use the tribe_events_register_event_cat_type_args filter that allows you to modify what gets sent to register_taxonomy()

Please let me know how this goes for you.

[Cliff]

Hi, Gerald. Sorry you’re experiencing this frustration.

I don’t know what code is in your custom plugin, but if you deactivate that custom plugin, do your Event Tickets Plus (ET+) Attendee Information fields then appear (one per ticket being purchased), as expected?

If yes, please describe the expected functionality of your custom plugin and possibly share a copy of it in a private reply if you choose.

[Cliff]

Hi, Daniel. Sorry you’re experiencing this high-priority known bug.

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, Sylvia.

Here’s a GIF of what the Tribe Bar can already do: https://cl.ly/0b3M3c2S1H1S — is this not sufficient?

If not, I’ll have to say the same thing I did in the thread you created this thread from:

I can point you to https://theeventscalendar.com/knowledgebase/creating-custom-filters-for-filter-bar/ but beyond that we’d be in custom development territory, which we don’t provide, 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]

Hi, Vincent.

Tickets/Attendees should only be added via the single event page, not directly in wp-admin (like in WooCommerce’s Products or anywhere else). This is because the WooCommerce checkout process–when a ticket is in the order–does the things it needs to do, like record the attendee, process the ticket’s additional fields, and adjust the remaining stock available.

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

[Cliff]

Hi, Ryan/Ty. 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.

[Author]

Posts