Hi @k4media ,
Thank you for reaching out. Our products team is aware of this issue and is working on a fix.
We prioritize bugs by taking into consideration the number of users impacted as well as how the bug impacts one’s ability to run an event/sell tickets. I don’t have a specific timeline as to when this issue will be resolved, but trust that our team is aware. Our team communicates updates and bug fixes in our newsletter and via our changelog.
In the meantime, the recommended action is to delete all rows from the shepherd_tec_tasks table and apply the following code snippet to prevent further build-up of the said table.
add_action( 'tribe_common_loaded', function () { remove_action( 'init', [ tribe( TEC\Common\StellarWP\Shepherd\Regulator::class ), 'schedule_cleanup_task' ], 20 ); } );
Your patience on this matter is highly appreciated.
—
Internal Bug Ticket Reference: TCMN-193
Plugin Support
Darian
(@d0153)
Hi there,
It looks like we haven’t heard back from you in a while, so I’ll go ahead and close this thread for now. Rest assured, we will update you once the fix is out.
If you still need assistance, feel free to reopen this thread or start a new one
Hi,
We also observed a similar issue on one of our users WP install (I work for a WordPress hosting company).
From our analysis the issue seems to be that the plugin code expects the shepherd_tec_tasks table to use the InnoDB engine, but on our server the default is MyISAM.
@k4media could this be the same cause for your issue too? Could you please check which DB engine is the default one on your DB and the one used for the table?
You should be able to do such checks via the following queries:
SHOW ENGINES; -- Check for the value "DEFAULT" in the "support" column
SHOW TABLE STATUS WHERE name = "wp_shepherd_tec_tasks";
Plugin Support
Darian
(@d0153)
Hi @karl94
Thanks so much for reaching out and for taking the time to share your findings. I’ve forwarded this information to our team for further review so we can take a closer look and address it accordingly.
So where do you add this add_action? Still seeing the buildup in the table.
Plugin Support
Darian
(@d0153)
Hi @stevea715
You can refer to this Knowledgebase article for guidance on adding custom code snippets: https://theeventscalendar.com/knowledgebase/best-practices-for-implementing-custom-code-snippets/
If you have any questions or concerns, please open a separate support thread so we can properly assist you in accordance with the WordPress Forum Guidelines.
I did this mod, placing the code above in the theme functions.php.
It did not fix the issue. This morning there are multiple records in the table. This is on the latest version.
Is this going to be fixed?
shepherd_tec_tasks
(32, 944601, 'e6d6e78562dee30b84c71e12e92eed58', 'shepherd_tidy_0c5564376533f4104430960ec7f98393', '{\"args\":[],\"task_class\":\"TEC\\\\Common\\\\StellarWP\\\\Shepherd\\\\Tasks\\\\Herding\"}', 0),
(31, 944599, 'e6d6e78562dee30b84c71e12e92eed58', 'shepherd_tidy_0c5564376533f4104430960ec7f98393', '{\"args\":[],\"task_class\":\"TEC\\\\Common\\\\StellarWP\\\\Shepherd\\\\Tasks\\\\Herding\"}', 0),
(30, 944597, 'e6d6e78562dee30b84c71e12e92eed58', 'shepherd_tidy_0c5564376533f4104430960ec7f98393', '{\"args\":[],\"task_class\":\"TEC\\\\Common\\\\StellarWP\\\\Shepherd\\\\Tasks\\\\Herding\"}', 0);
Plugin Support
Darian
(@d0153)
Hi @stevea715
Thanks for your response.
If you haven’t already done so, please try clearing the shepherd_tec_tasks table. If the snippet is still active, it should help prevent the table from being flooded with records.
If the issue persists, kindly open a new support thread and include all the details you’ve gathered so far. This will allow me to assist you more effectively and also ensure we’re adhering to the official WordPress Forum guidelines:
https://wordpress.org/support/forum-user-guide/faq/#i-have-the-same-problem-can-i-just-reply-to-someone-elses-post-with-me-too
I know you would rather I open a new support ticket and I DID DO THAT.
Two of my websites crashed Friday when Event Tickets was upgraded to 5.27.0. The site was limping along on the previous revision (Running very slow probably due to the snippet running often – because the basic cause of our issues has not been fixed).
My ISP had to recover (removed the wp_shepard_tec_tasks and other changes.)
We may have the same issue with the wp_shepherd_tec_tasks table. It was also using MyISAM. My ISP just changed all my tables to InnoDB engine and that “?may?” have solved the issue. I will not activate Event Tickets again regardless of the revision because I cannot suffer another crash of the websites.
HOWEVER, After sending multiple emails with error details, database errors, Etc. that were involved in the crashes I have YET to hear back if the issue is solved with the table engine change.
If that is the cause we just need a reply that will solve the issue.
Or, another possibility? Some website developers (like me) may have stopped using the Tickets Pro without deleting and then installing the free version of Event Tickets. All the old tables for the pro version still exist.
Can we get some resolution THIS IS A PROBLEM FOR OTHER WEBSITES
Dennis Spanogle websites tocnm.org and arcc.club
Plugin Support
Darian
(@d0153)
Hi @dspanogle
Thank you so much for providing such detailed information and for explaining your situation so clearly. I understand how frustrating it must be to have both of your websites affected, and your concerns are completely valid.
After checking with our team, I can confirm that the latest version of The Events Calendar plugin should resolve the issue related to the _shepherd_tec_tasks table. If you’re experiencing a problem specifically after updating Event Tickets, this may be a separate issue. I also see that you’ve already contacted our Help Desk, and one of my colleagues is actively assisting you with this.
If you have any further questions or need additional help, please don’t hesitate to let us know. We’re here to support you every step of the way!
