[Cliff]

Hi, Helge.

Could you please provide me these 3 URLs:

1. The URL you’re importing via Event Aggregator
2. A link to one of the events this is happening for — a link to the source
3. And this imported event’s link on your site (after imported via Event Aggregator)

Thank you.

[Cliff]

Hi, Chris.

Thanks for your detailed question.

I expect the “You already have tickets” sort of message is right above the “Buy tickets” form for the reason you stated — so hopefully they see it when at the Tickets section of the single events page.

You might simply add some more “vibrant” styling to make it stand out. For example:

body.single-tribe_events .tribe-link-tickets-message {
border: 5px solid red;
}

Looks like this: https://cl.ly/0x2l130H3k0T

Please let me know what you think of this.

[Cliff]

Hi. Thanks for your detailed request.

PayPal’s split payments functionality is only available via Community Tickets, which does require several of our paid plugins. I’d recommend checking out the Community Manager Bundle if you’re interested.

The reason this functionality is only available via Community Tickets is because each WordPress user would need to setup their own PayPal email address before adding a ticket to an event they create via the Community Events front-end form.

We also have this snippet available that might come in handy:

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

If you don’t think Community Tickets will work for you (having users create events and tickets via the Community Events front-end editing experience), please provide details why so I can better understand.

Thank you.

[Cliff]

Hi, Matt. Thanks for your question.

We don’t provide support for Avada. Their theme integrates our plugin with their theme; we do not take part in their doing this.

Their theme also customizes the views we provide, and they may offer additional views of data from our events plugin.

Therefore, please contact Avada support for such questions.

If they refer you back to us for reporting a bug, we’d be happy to handle that part of it. 🙂

Please let me know how this goes for you.

[Cliff]

Hi. Thanks for using our plugins.

I believe you’re requesting the same thing as one of our existing feature requests: https://tribe.uservoice.com/forums/195723-feature-ideas/suggestions/16852576-let-users-import-events-from-other-ecp-installs-vi

Please do add your vote there.

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

Thank you.

[Cliff]

Hi, Jason.

Neither of those PHP lines should be required. Our plugin already enables Featured Image support for the custom post type it registers.

When creating/editing an event in wp-admin, click Screen Options in the upper-right corner of your screen, then check the Featured Image box: https://cl.ly/1h3y0m0f1o2C

Then you should be able to see the Featured Image meta box in your wp-admin event edit screens.

Please let me know how this goes for you.

[Cliff]

Hi. Thanks for your screenshot.

It looks like you’re asking about Event Tickets Plus’ Attendee Meta fields.

Could you please provide me a link to this specific event the screenshot is from and also provide me a screenshot of this ticket’s settings from your wp-admin event edit screen?

Thank you.

[Cliff]

Hi, Maximilian.

Thanks for your detailed question and the updates. I’m glad you’re making progress with your customization.

You can see how our plugin uses register_taxonomy, here: https://github.com/moderntribe/the-events-calendar/blob/4.3.5/src/Tribe/Main.php#L1473-L1508

Maybe that will help.

If you still need assistance, please clarify:

1. It sounds like you do NOT want to display non-Event posts. Is this correct?
2. If yes, why not just use Event Categories, that gets registered for you?

You could utilize PRO’s Additional Fields to create a radio, checkbox, drop-down, or other type of “Region” field.

Then Filter Bar could enable filtering by these regions. You could edit Filter Bar’s settings at wp-admin > Events > Settings > Filter Bar tab

They wouldn’t be true “taxonomies”, but you could use them for such categorization and directly link to them, like this (but it’s filtering Venues, not a PRO Additional Field because we don’t have that setup on our demo site): http://wpshindig.com/events/list/?tribe_venues=29433

Looking forward to hearing back from you…

[Cliff]

Hi, Aurelien.

You could utilize PRO’s Additional Fields to create a radio, checkbox, drop-down, or other type of “Region” field.

Then Filter Bar could enable filtering by these regions. You could edit Filter Bar’s settings at wp-admin > Events > Settings > Filter Bar tab

Please let me know if this fully answers your question.

[Cliff]

Hi, Chris.

I’m not clear what exactly you’re requesting.

Are you saying you do want RSVP tickets available to be added… but if an Event Tickets Plus (ET+) ticket (like WooCommerce or Easy Digital Downloads) is added to the event, then you’d want the RSVP tickets to no longer be viewable for this single event?

Please clarify so I can advise accurately.

Thank you.

[Cliff]

Hi again, Jennifer.

I installed and activated ‘x’ and ‘x-child’ themes and tried creating a recurring event with each and they both worked just fine.

Also, I looked into the code in your ‘x-child’ theme and there really wasn’t any code in there so it’s unlikely it has any effect on 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 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]

Hi, Dan.

Event Tickets Plus (ET+) uses your eCommerce plugin for checkout. Your eCommerce plugin will need to be the one to create and apply coupon codes.

If you’re using WooCommerce, for example, you could create a coupon that applies only to a specific Ticket (product) and test to make sure it works how you want (such as only taking $10 off Ticket ID # 472)

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

[Cliff]

Hi. Thanks for your detailed question and sorry to hear of the troubles you’re having.

You didn’t misunderstand, but we do not guarantee support with any themes or provide theme-specific usage support, per our Scope of Support / Terms.

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

Also, your link didn’t work for me (as if the domain is incorrect).

One thing we recommend, just for testing is to please enable WP_DEBUG and WP_DEBUG_LOG and share any debug messages you see while using your theme’s builder, navigating your site’s home page, events page, single-event pages, and any other of your site’s pages relevant to this ticket.

[Cliff]

Hi, Florian. Here’s a code snippet to implement <noscript>:

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

FYI: It’s scheduled (no guarantees) to have a fix within the next couple of weeks (I don’t know what it might look like) so this snippet may be unnecessary / duplicative once that comes out.

[Cliff]

Hi, Bruce. Here’s a code snippet to implement <noscript>:

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

FYI: It’s scheduled (no guarantees) to have a fix within the next couple of weeks (I don’t know what it might look like) so this snippet may be unnecessary / duplicative once that comes out.

[Author]

Posts