[Cliff]

Thank you for your detailed report, of both the theme you were using and of the code you found.

In our experience, most issues are resolved by either the individual finding it’s some sort of conflict or we get multiple reports of the same issue and confirm it as a bug. It’s rare when the issue isn’t a bug and is actually from our plugin’s code, like you’ve found for your use case.

Again, kudos on figuring that out, but I still do not know where in your site you’re seeing this, what theme you’re using, what your system information settings are, etc. For example, in this scenario, if I had known which URL it was at, I could have looked in that template file to see which functions are used and then dig deeper through those and likely come to the same conclusion as you did.

It’s challenging to give full support and the best suggestions without having all that information.

Hopefully, you’ll be able to provide more details for your future support requests and we’ll be able to provide quicker, more thorough service to you.

We definitely appreciate your business and want to be as helpful as possible throughout your time with us.

Have a great week!

[Cliff]

Thanks for that jam-packed update.

Please enable WP_DEBUG and WP_DEBUG_LOG and share any debug messages you see while in wp-admin, 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.

WP_DEBUG messages would be the first place to look for big errors/issues like this.

[Cliff]

Thanks for the update.

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]

Thanks for sharing.

What about just filtering the URL that gets used by our plugin. Maybe something along the lines of https://gist.github.com/cliffordp/9d6c25feb389f98e8ae09a41273a3488 or even using add_query_arg()

[Cliff]

I will not be able to provide you with my IP address.

[Cliff]

The only way to verify the error must be coming from our plugin(s) is if you do the testing required to actually verify this. I know it can be time-consuming and worrisome to change things on your site, but this is a good reason for using a staging/development server. You might want to ask your web host about that.

If you do find a way to reproduce the issue consistently (such as a specific theme or plugin that, when activated, causes the issue — or some combination of settings and event data) and communicate it to me, I’ll be happy to try replicating the issue. If I can, we’ll file a bug report and proceed from there.

[Cliff]

This reply is private.

[Cliff]

Hi, David.

I visited that link, but it requires a password.

Could you please provide details on how you test-purchased it, such as using WooCommerce and bought the ticket with PayPal?

Thank you.

[Cliff]

Hi, Charles. Thank you for reporting this. I found the errant code at https://github.com/moderntribe/tribe-common/blob/4.3.4/src/Tribe/Main.php#L287

This is a rare scenario where it’s probably okay to just edit the core plugin files to remove this little typo from all 3 of these files:

• /wp-content/plugins/event-tickets/common/src/Tribe/Main.php
• /wp-content/plugins/the-events-calendar/common/src/Tribe/Main.php
• /wp-content/plugins/the-events-calendar/vendor/tickets/common/src/Tribe/Main.php

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.

Thank you for your detailed question.

In our forums we keep our threads focused on just one issue at a time to ensure we fully answer each of your questions/issues. Please keep this in mind for the future and start a new thread for your additional questions from this thread. Thanks for your understanding, and I’ll reply here only your second question. Please re-post your first question in a new thread.

Thank you for reporting this. I found the errant code at https://github.com/moderntribe/tribe-common/blob/4.3.4/src/Tribe/Main.php#L287

This is a rare scenario where it’s probably okay to just edit the core plugin files to remove this little typo from all 3 of these files:

• /wp-content/plugins/event-tickets/common/src/Tribe/Main.php
• /wp-content/plugins/the-events-calendar/common/src/Tribe/Main.php
• /wp-content/plugins/the-events-calendar/vendor/tickets/common/src/Tribe/Main.php

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]

Thank you for reporting this. I found the errant code at https://github.com/moderntribe/tribe-common/blob/4.3.4/src/Tribe/Main.php#L287

This is a rare scenario where it’s probably okay to just edit the core plugin files to remove this little typo from all 3 of these files:

• /wp-content/plugins/event-tickets/common/src/Tribe/Main.php
• /wp-content/plugins/the-events-calendar/common/src/Tribe/Main.php
• /wp-content/plugins/the-events-calendar/vendor/tickets/common/src/Tribe/Main.php

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]

Thank you for reporting this. I found the errant code at https://github.com/moderntribe/tribe-common/blob/4.3.4/src/Tribe/Main.php#L287, like Jon mentioned.

This is a rare scenario where it’s probably okay to just edit the core plugin files to remove this little typo from all 3 of these files:

• /wp-content/plugins/event-tickets/common/src/Tribe/Main.php
• /wp-content/plugins/the-events-calendar/common/src/Tribe/Main.php
• /wp-content/plugins/the-events-calendar/vendor/tickets/common/src/Tribe/Main.php

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, Estelle. Sorry you’re experiencing this.

Since I wasn’t able to recreate this issue on my testing site and I haven’t seen others reporting this, I’d suggest following these recommended troubleshooting steps for your own site:

I see you have many plugins active. 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, Chris.

If you provide the URL for an event that this is happening for, I might be able to help with this.

Thank you.

[Cliff]

Hi, Doug.

Please reference https://theeventscalendar.com/knowledgebase/pro-recurring-events/#breaking-off-events

You might have edited a single occurrence from the recurrence series, thereby breaking it from the series.

Please let me know if this answers your question.

[Author]

Posts