[Cliff]

Steve, that’s great progress. Those two with thousands of child posts are definitely the likely offenders. Good find!

However, no screenshots came through. 🙁

And I also saw you opened another thread for the same topic at https://theeventscalendar.com/support/forums/topic/very-urgent-issue-with-recurrence-instances/ and got a response there so I will close this one out and let that newer one continue.

Thank you again for your efforts here and sorry this happened.

[Cliff]

This reply is private.

[Cliff]

Event Tickets Plus (ET+) is an add-on for our free Event Tickets (ET) plugin, just like our PRO is an add-on for our free The Events Calendar (TEC) plugin.

Event Tickets can work with TEC’s events, of course, but it can also work on other post types.

ET doesn’t allow selling of paid tickets; that’s what ET+ enables.

When you have ET+, the ticket you create for an event gets created while editing that single event in wp-admin and the visitor purchasing goes through WooCommerce’s checkout system, but you create/edit/manage each event’s tickets from each event, not from the WooCommerce wp-admin screens.

Again, ET and ET+ can work with TEC or TEC PRO or regular WordPress posts or other custom post types.

If you have follow-up questions, I’d suggest you refer to our New User Primer for ET+ and give it a spin within our refund timeframe.

I hope this clears things up 🙂

[Cliff]

We really don’t.

Again, the issue could be the bug introduced in Pro version 4.2.2, in which case I’d suggest starting with the events modified most recently (on or after the date you updated to v4.2.2) and clicking that “fix” button on each of those parent events that are a recurring series.

This SQL query may help in that instance (enter your own date):

SELECT DISTINCT( post_parent ), post_date
FROM   wp_posts

WHERE post_parent > 0
  AND post_type = 'tribe_events'
  AND post_date > '2016-07-01'

ORDER BY post_date DESC

LIMIT 100

Another possibility is that there’s a legitimate user error, like setting a recurrence rule like this:

• trying to enter a date
• leaving the recurrence count empty

These are 2 types of user errors that we have on our to-do list to protect against in the future, either/both of which can cause a lot of events within a recurrence series.

Please let me know what you find out.

[Cliff]

Sure. Start by looking at this file: /wp-content/plugins/the-events-calendar-community-events/src/views/community/edit-event.php

And if you want to edit that file, it tells you where to copy-paste-edit it in the top of the comments.

Let me know if you need anything else.

[Cliff]

I know some users have tried WooCommerce variable pricing, but here’s our official answer: Compatibility with WooCommerce Extensions

[Cliff]

This reply is private.

[Cliff]

Yes, I’m asking you to disable all the other plugins & go through the process outlined on the Testing for Conflicts page.

[Cliff]

If the fix plugin isn’t solving your issue, it could be that your recurring events aren’t actually affected by the bug from version 4.2.2 but instead are simply misconfigured. Can you share some screenshots of recurring events you think are resulting in an unacceptably large number of generated events (so we can see the recurrence rules)?

[Cliff]

Hi. Thanks for considering our plugin suite.

To sell tickets, you’d need Event Tickets Plus and your choice of an eCommerce plugin (like WooCommerce) to handle the actual checkout (receiving of money) process.

Basically, our plugin allows you to create a paid ticket and control when it’s available for purchase and to limit the quantity of each ticket. Then the checkout process goes to your eCommerce plugin’s “cart” to complete the checkout (so you’d limit payment options via your WooCommerce setup).

Last but not least, we have a pretty great Refund Policy so you can buy one or many of our add-ons and thoroughly test them.

Let me know if you have any follow-up questions.

[Cliff]

Hi. Thanks for considering our plugin suite.

To sell tickets, you’d need Event Tickets Plus and your choice of an eCommerce plugin (like WooCommerce) to handle the actual checkout (receiving of money) process.

Basically, our plugin allows you to create a paid ticket and control when it’s available for purchase and to limit the quantity of each ticket. Then the checkout process goes to your eCommerce plugin’s “cart” to complete the checkout.

So any upsell functionality would need to be a customization. It’s possible the eCommerce plugin’s shopping cart may be the proper place to include such an upsell.

Finally, our plugin wouldn’t have any support for generating a raffle ticket or even managing the stock of a raffle ticket (unless you issued them as separate Event Tickets Plus “tickets”) so this might be another area you could customize.

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

Last but not least, we have a pretty great Refund Policy so you can buy one or many of our add-ons and thoroughly test them.

Let me know if you have any follow-up questions.

[Cliff]

Hi Kate. You could hide certain fields via CSS or you could follow our Themer’s Guide to customize the Community Events form to your liking.

Please let me know if you need anything else.

[Cliff]

Hi Brent.

You’re thinking along correct lines, but you should leave the “events” slug alone.

Then you could add your own custom redirect from /events/ to /events/category/external/

and then require a certain logged-in user level to access /events/category/internal/

You’ll need to determine your best route of action to redirect (such as via a plugin or custom coding) and to control membership/access levels.

Let me know if there’s anything else I can help with.

[Cliff]

My apologies about that link not be accessible. Here’s a publicly-accessible version: https://cl.ly/400O3R3q3M1I

Yes, you’d need TEC core and TEC Pro active to run it… and yes it does require you to click it for each recurring event series (i.e. parent post) but not for each auto-generated occurrence within the series (i.e. child posts).

You can identify recurring events at wp-admin > Events > look for a “Yes” in the “Recurring” column.

If you’d like, here’s a snippet to make it so only the first/parent event appears in wp-admin:

https://gist.github.com/cliffordp/81f23a207ab483c9e7c6d910f9b29c0a

Another idea is to possibly search your wp_posts table for tribe_events post type with a creation or modified date that was around the time of your updating. This may help identify the number of runaways if the site users haven’t be creating a bunch of new events since then.

Please let me know how else I can help at this time.

[Cliff]

Sounds good. Thanks for the info. Best to you!

[Author]

Posts