Event Tickets, 5.13.1 – Fatal error… maybe_disable_foreign_key_checks

Hi @agilewarejustin ,

Thank you for reaching out.

Regrettably, I have not been able to reproduce this error in my testing environment running only The Events Calendar Version 6.6.1 and Event Tickets Version 5.13.1 plugin (see: https://pasteboard.co/Jh5FN1W0lThq.png) on a WordPress 6.6.1 environment.

That said, I suspect there’s a conflict that’s causing the issue here. It would be good to test for conflicts. Could you follow the following steps?

1. Deactivate all other plugins except for The Events Calendar Plugins.
2. Switching to the Default theme.

Please read the Testing for Conflicts Article before doing anything. 

To be safe, we’d recommend conducting tests and updates on a Staging Server. Also, please keep a working backup of your website.

Hi @agilewarejustin

It seems like this thread has been quiet for a bit, so we’ll go ahead and mark it as resolved. However, if any further questions or concerns come up, please don’t hesitate to start a new thread.

For whatever reason, no arguments are being passed to the maybe_disable_foreign_key_checks function when by the before_run_command WP-CLI hook, https://github.com/wp-cli/wp-cli/blob/main/php/class-wp-cli.php#L238C8-L238C26

        public function maybe_disable_foreign_key_checks( array $args ): bool {
                if ( ! ( $args[0] === 'site' && $args[1] === 'empty' ) ) {
                        return false;
                }
                global $wpdb;
                $wpdb->query( 'SET FOREIGN_KEY_CHECKS=0;' );

                return true;
        }

However, checking if no arguments have been passed, guarding against this problem fixes the issue.

Below is the updated code.

      public function maybe_disable_foreign_key_checks( array $args = [] ): bool {
                if (empty($args) || $args[0] !== 'site' || $args[1] !== 'empty') {
                        return false;
                }
                global $wpdb;
                $wpdb->query( 'SET FOREIGN_KEY_CHECKS=0;' );

                return true;
        }

Hi @agilewarejustin ,

Thank you for your message and the information. I’ll be sure to share your feedback and your recommended fix with our product management team.

Hi @agilewarejustin

One of my colleagues suggested disabling the foreign key checks before running the command and then turning them back on afterwards:

See example:

wp db query "SET FOREIGN_KEY_CHECKS=0;" --url=https://www.test.org.au --
path=/home/test/public_html 

wp --user=cron --url=https://www.test.org.au --path=/home/test/public_html cron event run --due-now 

wp db query "SET FOREIGN_KEY_CHECKS=1;" --url=https://www.test.org.au --path=/home/test/public_html

As always, please test it first on a staging site before applying to your live site.

A better solution is to fix the code as indicated previously.

Until that happens, then disabling the Event Tickets plugin for cron jobs will work going forward.

wp --user=cron --url=https://www.test.org.au --path=/home/test/public_html --skip-plugins=event-tickets cron event run --due-now

Hi @agilewarejustin

Thank you for providing your input. I want to assure you that your feedback will be shared with the rest of the team for their review. Meanwhile, we have generated an internal ticket [TECTRIA-312] dedicated to resolving this issue. I have also included your specific use case in the ticket to ensure that it is communicated effectively to our team.

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.

I’m happy to help if any other questions are coming up around this topic, otherwise I’ll go ahead and close this ticket.

Thanks again for reporting this issue and for using The Events Calendar! Have a great day.

—

Internal Bug Ticket Reference: TECTRIA-312