Forum Replies Created
-
Posts
-
I understand the issue and apologize for it not working well for you at this time. We’re (always) working hard to squash bugs!
Please reference our Refund Policy page and let me know if you have any follow-up questions.
Thanks for your feedback.
You may want to add your vote to this existing feature request: https://tribe.uservoice.com/forums/195723-feature-ideas/suggestions/5115736-show-amount-of-events-for-each-pin-marker-in-map-v
You can search for another feature request or add your own there too.
Thanks for letting me know this thread is resolved. Have a great day!
Gene,
Thank you for posting! In this forum we try to keep our threads focused on just one user’s problem. This ensures that we are addressing your specific problem instead of a general group one, and not possibly missing anything unique your situation.
To that end, would you mind opening up a new topic here about your issue? If you could please detail in your own words exactly what your problem is (instead of just linking here), that will go a long way toward helping you get this issue resolved as fast as possible. I hope you understand our reasoning here and do not mind this extra step, we have just found it serves our users best.
===
Tyler, please get back to me when you can.
===
Thanks to you both.
Robert, one of our developers passed along this update:
For this Fatal in WooCommerce Tickets 3.12.x – Fatal error: Class ‘Tribe__Tickets__Attendance” on the attendees list please have people redownload The Events Calendar core as the file is now there. It was missing and caused the fatal.
In other words, please delete The Events Calendar from your site. Then re-download it from https://wordpress.org/plugins/the-events-calendar/ and install that fresh copy, either via SFTP or the WordPress plugin installer.
Then make sure The Events Calendar gets re-activated.
Please let me know how things go for you.
Hi Robert.
Thanks for reporting this issue with WooTickets (legacy plugin, not Event Tickets Plus) and sharing your system information.
It is a known bug that is expected to be fixed in our next release, which I’d guess will be in 1-2 weeks.
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.
===
P.S. Have you tried switching to Event Tickets Plus yet?
Hi William.
Thanks for your thorough request. This sounds like a valuable (although potentially complex) enhancement.
Unfortunately, I’m not able to provide you with a code snippet to pull something like this off.
I would encourage you to search for or add a new feature request at our plugins’ UserVoice page.
This allows others who are interested in that feature to easily voice their support. We frequently review suggestions there to find out which ones are popular, then we implement as many of them as we can.
Once you post it, feel free to link to it from here in case anyone comes across this forum thread in the future.
If you really do need this feature sooner than we can deliver it and need some coding help, you may want to ask your developer or reference our list of known customizers.
Thank you.
Hi Rika. Thanks for the link.
This is what I saw around 11:32pm Central Time on June 15: http://cl.ly/430n2t0D3P3U
The Events List widgets you have there seem to be working as you’re wanting them to.
If not, please provide additional information.
Thank you.
Hi Chris. Sorry you’re experiencing this. I’ll do my best to help quickly and thoroughly.
Anytime you have a 500 error, there’s something wrong with your system — malware, incomplete updates, rogue plugin, bad code in your theme, etc.
One thing specific to our PRO plugin that it could be is if you created a recurring event with no end date (recurring forever), which creates waaay too many events. You can read more about it here: https://theeventscalendar.com/knowledgebase/pro-recurring-events/#make-recurring
I’m guessing that’s not the issue though.
I’d suggest following general troubleshooting steps. Here are some ideas that may help (no guarantees or promises):
- ask your web host for any error logs to point you in the right direction
- switch to a WordPress default theme like TwentyFourteen, TwentyFifteen, TwentySixteen, etc. If you don’t have access to your site’s wp-admin area at all, you’ll need to rename the wp-content/themes/your-theme folder to wp-content/themes/x-your-theme or something to unset it as the current theme.
- rename your wp-content/plugins folder to wp-content/x-plugins or something else to deactivate ALL your site’s plugins. Then set it back to /plugins and enable your plugins one-by-one to test which plugin makes the 500 error come back.
- manually update WordPress core files (since you said you’re having an issue updating). I’d be curious to know what issue you’re experiencing.
I hope you get it sorted quickly!
Let me know if you think I can be of any further assistance in this matter.
Hi Antonio Jose. Sorry you’re having trouble with oEmbed.
Could you please make sure all your Modern Tribe plugins (and WordPress core) are at their latest versions?
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 and see if that helps narrow down the cause of this.
If it doesn’t, please share your System Information. That will give me a lot of extra information to help diagnose the problem.
Let us know what you find out.
Thanks.
Hi. Thanks for your detailed question.
We’ve seen this issue on sites running an out-of-date version of WordPress.
There were one or more releases since our last interaction. Could you please make sure all your Modern Tribe plugins (and WordPress core) are at their latest versions?
Once you verify you’re on the latest versions, please test to see if the issue is still happening for you.
Thanks!
Hi Jane. Sorry this is affecting you.
Unfortunately, this is a current 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.
(FYI: My best guess is that a fix will be released within 1-2 weeks.)
P.S. You may want to check out this additional information for a possible (but risky) workaround.
