Update to 5.16 crashes
-
Event Tickets 5.16 crashes with The Events Calendar 6.8. I rolled back to 5.15 and then had to roll back The Events Calendar as well to 6.7.1 since 6.8 would not work with 5.15 and prompted me to update. Tickets 5.15 and The Events Calendar 6.7.1 works fine.
The page I need help with: [log in to see the link]
-
Hi @girlbot
Thanks for reaching out.
Could you please share the specific error message you received when you encountered the issue? If you don’t have that on hand, it would be really helpful if you could check your server for any error logs. This information will assist us in investigating the problem more thoroughly.
Additionally, could you provide the name of your hosting provider, as well as the versions of WordPress and PHP that you are currently using? This will allow us to understand your setup better as we work on resolving the issue. Thank you!
@d0153
We just experienced the same fatal error as well when updating to Events Calendar 6.8.This is the info I got back:
WordPress version 6.6.2
Active theme: Twenty Twenty-Four (version 1.2)
Current plugin: Event Tickets (version 5.16.0)
PHP version 8.2.18 Error DetailsAn error of type E_ERROR was caused in line 296 of the file /home/nceclect/public_html/wp-content/plugins/event-tickets/common/vendor/vendor-prefixed/stellarwp/db/src/DB/DB.php. Error message: Uncaught TEC\Common\StellarWP\DB\Database\Exceptions\DatabaseQueryException: Database Query in /home/nceclect/public_html/wp-content/plugins/event-tickets/common/vendor/vendor-prefixed/stellarwp/db/src/DB/DB.php:296
Stack trace: 0 /home/nceclect/public_html/wp-content/plugins/event-tickets/common/vendor/vendor-prefixed/stellarwp/db/src/DB/DB.php(81): TEC\Common\StellarWP\DB\DB::runQueryWithErrorChecking(Object(Closure)) 1 /home/nceclect/public_html/wp-content/plugins/event-tickets/common/vendor/vendor-prefixed/stellarwp/schema/src/Schema/Tables/Contracts/Table.php(504): TEC\Common\StellarWP\DB\DB::delta(‘\n\t\t\tCREATE TABL…’) 2 /home/nceclect/public_html/wp-content/plugins/event-tickets/common/vendor/vendor-prefixed/stellarwp/schema/src/Schema/Builder.php(277): TEC\Common\StellarWP\Schema\Tables\Contracts\Table->update() 3 /home/nceclect/public_html/wp-content/plugins/event-tickets/common/vendor/vendor-prefixed/stellarwp/schema/src/Schema/Register.php(138): TEC\Common\StellarWP\Schema\Builder->up() 4 /home/nceclect/public_html/wp-content/plugins/event-tickets/src/Tickets/Seating/Tables.php(48): TEC\Common\StellarWP\Schema\Register::table(Object(TEC\Tickets\Seating\Tables\Sessions)) 5 /home/nceclect/public_html/wp-content/plugins/event-tickets/common/src/Common/Contracts/Provider/Controller.php(49): TEC\Tickets\Seating\Tables->do_register() 6 /home/nceclect/public_html/wp-content/plugins/event-tickets/common/vendor/vendor-prefixed/lucatume/di52/src/Container.php(462): TEC\Common\Contracts\Provider\Controller->register() 7 /home/nceclect/public_html/wp-content/plugins/event-tickets/common/src/Common/Contracts/Container.php(46): TEC\Common\lucatume\DI52\Container->register(‘TEC\Tickets\Sea…’) 8 /home/nceclect/public_html/wp-content/plugins/event-tickets/src/Tickets/Seating/Controller.php(118): TEC\Common\Contracts\Container->register(‘TEC\Tickets\Sea…’) 9 /home/nceclect/public_html/wp-content/plugins/event-tickets/common/src/Common/Contracts/Provider/Controller.php(49): TEC\Tickets\Seating\Controller->do_register() 10 /home/nceclect/public_html/wp-content/plugins/event-tickets/common/vendor/vendor-prefixed/lucatume/di52/src/Container.php(462): TEC\Common\Contracts\Provider\Controller->register() 11 /home/nceclect/public_html/wp-content/plugins/event-tickets/common/src/Common/Contracts/Container.php(46): TEC\Common\lucatume\DI52\Container->register(‘TEC\Tickets\Sea…’) 12 /home/nceclect/public_html/wp-content/plugins/event-tickets/src/Tickets/Provider.php(101): TEC\Common\Contracts\Container->register(‘TEC\Tickets\Sea…’) 13 /home/nceclect/public_html/wp-content/plugins/event-tickets/common/vendor/vendor-prefixed/lucatume/di52/src/Container.php(462): TEC\Tickets\Provider->register() 14 /home/nceclect/public_html/wp-content/plugins/event-tickets/common/src/Common/Contracts/Container.php(46): TEC\Common\lucatume\DI52\Container->register(‘TEC\Tickets\Pro…’) 15 /home/nceclect/public_html/wp-content/plugins/event-tickets/common/src/Tribe/Container.php(305): TEC\Common\Contracts\Container->register(‘TEC\Tickets\Pro…’) 16 /home/nceclect/public_html/wp-content/plugins/event-tickets/src/Tribe/Main.php(458): tribe_register_provider(‘TEC\Tickets\Pro…’) 17 /home/nceclect/public_html/wp-content/plugins/event-tickets/src/Tribe/Main.php(428): Tribe__Tickets__Main->bind_implementations() 18 /home/nceclect/public_html/wp-includes/class-wp-hook.php(324): Tribe__Tickets__Main->bootstrap(”) 19 /home/nceclect/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(”, Array) 20 /home/nceclect/public_html/wp-includes/plugin.php(517): WP_Hook->do_action(Array) 21 /home/nceclect/public_html/wp-content/plugins/event-tickets/common/src/Tribe/Main.php(128): do_action(‘tribe_common_lo…’) 22 /home/nceclect/public_html/wp-includes/class-wp-hook.php(324): Tribe__Main->plugins_loaded(”) 23 /home/nceclect/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array) 24 /home/nceclect/public_html/wp-includes/plugin.php(517): WP_Hook->do_action(Array) 25 /home/nceclect/public_html/wp-settings.php(555): do_action(‘plugins_loaded’) 26 /home/nceclect/public_html/wp-config.php(104): require_once(‘/home/nceclect/…’) 27 /home/nceclect/public_html/wp-load.php(50): require_once(‘/home/nceclect/…’) 28 /home/nceclect/public_html/wp-admin/admin.php(34): require_once(‘/home/nceclect/…’) 29 /home/nceclect/public_html/wp-admin/plugins.php(10): require_once(‘/home/nceclect/…’) 30 {main}thrown
We have the same issue as well.
[30-Oct-2024 18:03:24 UTC] WordPress database error Specified key was too long; max key length is 1000 bytes for query CREATE TABLE
wp_tec_slr_sessions
(token
varchar(255) NOT NULL,object_id
bigint(20) NOT NULL,expiration
int(11) NOT NULL,reservations
longblob DEFAULT ”, PRIMARY KEY (token
) ) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci made by require_once(‘wp-config.php’), require_once(‘wp-settings.php’), do_action(‘plugins_loaded’), WP_Hook->do_action, WP_Hook->apply_filters, Tribe__Main->plugins_loaded, do_action(‘tribe_common_loaded’), WP_Hook->do_action, WP_Hook->apply_filters, Tribe__Tickets__Main->bootstrap, Tribe__Tickets__Main->bind_implementations, tribe_register_provider, TEC\Common\Contracts\Container->register, TEC\Common\lucatume\DI52\Container->register, TEC\Tickets\Provider->register, TEC\Common\Contracts\Container->register, TEC\Common\lucatume\DI52\Container->register, TEC\Common\Contracts\Provider\Controller->register, TEC\Tickets\Seating\Controller->do_register, TEC\Common\Contracts\Container->register, TEC\Common\lucatume\DI52\Container->register, TEC\Common\Contracts\Provider\Controller->register, TEC\Tickets\Seating\Tables->do_register, TEC\Common\StellarWP\Schema\Register::table, TEC\Common\StellarWP\Schema\Builder->up, TEC\Common\StellarWP\Schema\Tables\Contracts\Table->update, TEC\Common\StellarWP\DB\DB::delta, TEC\Common\StellarWP\DB\DB::runQueryWithErrorChecking, TEC\Common\StellarWP\DB\DB::TEC\Common\StellarWP\DB\{closure}, dbDelta [30-Oct-2024 18:04:08 UTC] WordPress database error Specified key was too long; max key length is 1000 bytes for query CREATE TABLEwp_tec_slr_sessions
(token
varchar(255) NOT NULL,object_id
bigint(20) NOT NULL,expiration
int(11) NOT NULL,reservations
longblob DEFAULT ”, PRIMARY KEY (token
) ) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci made by require_once(‘wp-admin/admin.php’), require_once(‘wp-load.php’), require_once(‘wp-config.php’), require_once(‘wp-settings.php’), do_action(‘plugins_loaded’), WP_Hook->do_action, WP_Hook->apply_filters, Tribe__Main->plugins_loaded, do_action(‘tribe_common_loaded’), WP_Hook->do_action, WP_Hook->apply_filters, Tribe__Tickets__Main->bootstrap, Tribe__Tickets__Main->bind_implementations, tribe_register_provider, TEC\Common\Contracts\Container->register, TEC\Common\lucatume\DI52\Container->register, TEC\Tickets\Provider->register, TEC\Common\Contracts\Container->register, TEC\Common\lucatume\DI52\Container->register, TEC\Common\Contracts\Provider\Controller->register, TEC\Tickets\Seating\Controller->do_register, TEC\Common\Contracts\Container->register, TEC\Common\lucatume\DI52\Container->register, TEC\Common\Contracts\Provider\Controller->register, TEC\Tickets\Seating\Tables->do_register, TEC\Common\StellarWP\Schema\Register::table, TEC\Common\StellarWP\Schema\Builder->up, TEC\Common\StellarWP\Schema\Tables\Contracts\Table->update, TEC\Common\StellarWP\DB\DB::delta, TEC\Common\StellarWP\DB\DB::runQueryWithErrorChecking, TEC\Common\StellarWP\DB\DB::TEC\Common\StellarWP\DB\{closure}, dbDelta [30-Oct-2024 18:04:08 UTC] PHP Fatal error: Uncaught TEC\Common\StellarWP\DB\Database\Exceptions\DatabaseQueryException: Database Query in /home/iclowdown/public_html/wp-content/plugins/event-tickets/common/vendor/vendor-prefixed/stellarwp/db/src/DB/DB.php:296 Stack trace: #0 /home/iclowdown/public_html/wp-content/plugins/event-tickets/common/vendor/vendor-prefixed/stellarwp/db/src/DB/DB.php(84): TEC\Common\StellarWP\DB\DB::runQueryWithErrorChecking(Object(Closure)) #1 /home/iclowdown/public_html/wp-content/plugins/event-tickets/common/vendor/vendor-prefixed/stellarwp/schema/src/Schema/Tables/Contracts/Table.php(504): TEC\Common\StellarWP\DB\DB::delta(‘\n\t\t\tCREATE TABL…’) #2 /home/iclowdown/public_html/wp-content/plugins/event-tickets/common/vendor/vendor-prefixed/stellarwp/schema/src/Schema/Builder.php(277): TEC\Common\StellarWP\Schema\Tables\Contracts\Table->update() #3 /home/iclowdown/public_html/wp-content/plugins/event-tickets/common/vendor/vendor-prefixed/stellarwp/schema/src/Schema/Register.php(138): TEC\Common\StellarWP\Schema\Builder->up( in /home/iclowdown/public_html/wp-content/plugins/event-tickets/common/vendor/vendor-prefixed/stellarwp/db/src/DB/DB.php on line 296Hi @nceclecticesports @girlbot @vapidjimbo,
We’ve just released a version
5.16.0.1
that should resolve the problem you all are having related to your Database Engine not working with our previous Table settings.Best regards,
Perfect, thank you! Updating to the new version 5.16.0.1 seems to have resolved the issue for us.
Thanks,
Jim
This fixed it. Thank you!
Fixed for me with 5.16.01
- You must be logged in to reply to this topic.