axaak
Forum Replies Created
-
Thanks Ginger. I’ve submitted the requested info.
Forum: Plugins
In reply to: [The Events Calendar] Fatal error after 6.15.0.1 updateHi @darian,
many thanks for the quick reply. Before I uninstalled the plugin du showed a size of 50596 in the plugin’s directory. I then deleted the plugin and installed it again. The fatal error no longer appears even though du still shows 50596. This certainly isn’t conclusive but does suggest the files might be unchanged and may point to code that runs at install/activate time.
This is on a staging server. If we have the same problem on live we’ll try this reinstall first.Hi,
any thoughts or progress on this one please? We’d like to be on the latest version but it breaks our site.
Happy to help with debugging.@sounds I didn’t overwrite the plugin I did a plugin update to the lower version which may run hooks that your method does not,e.g.
wp plugin update give –version=3.22.2
Your database may be in an inconsistent state now. You may want to restore from your backup before trying the above.
HTH@gscoolidge you cannot run your DB updater because you get, “There has been a critical error on this website.” when trying to access it from the dashboard.
For others with this problem I downgraded to 3.22.2 then visited the Give ->Tools->Data Database updates and ran the one failed update. After that I was able to update the plugin. I actually did 4.1.1 first then the latest but you can probably go directly to the latest. YMMV.Downgrading to 2.2.28 fixes the problem – very different code.
We have the same error since upgrading this morning:
PHP Fatal error: Uncaught Give\Framework\Database\Exceptions\DatabaseQueryException: Database Query in /home//path/to/website/htdocs/wp-content/plugins/give/src/Framework/Database/DB.php:247\nStack trace:\n#0 /home//path/to/website/htdocs/wp-content/plugins/give/src/Framework/Database/DB.php(86): Give\Framework\Database\DB::runQueryWithErrorChecking()\n#1 /home//path/to/website/htdocs/wp-content/plugins/give/src/Framework/QueryBuilder/Concerns/CRUD.php(103): Give\Framework\Database\DB::__callStatic()\n#2 /home//path/to/website/htdocs/wp-content/plugins/give/src/FormBuilder/FormBuilderRouteBuilder.php(84): Give\Framework\QueryBuilder\QueryBuilder->get()\n#3 /home//path/to/website/htdocs/wp-content/plugins/give/src/FormBuilder/ServiceProvider.php(57): Give\FormBuilder\FormBuilderRouteBuilder->getUrl()\n#4 /home//path/to/website/htdocs/wp-includes/class-wp-hook.php(324): Give\FormBuilder\ServiceProvider::Give\FormBuilder\{closure}()\n#5 /home//path/to/website/htdocs/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()\n#6 /home//path/to/website/htdocs/wp-includes/plugin.php(517): WP_Hook->do_action()\n#7 /home//path/to/website/htdocs/wp-admin/admin-header.php(118): do_action()\n#8 /home//path/to/website/htdocs/wp-admin/index.php(137): require_once(‘…’)\n#9 {main}\n thrown in /home//path/to/website/htdocs/wp-content/plugins/give/src/Framework/Database/DB.php on line 247
I have deactivated the plugin for now. I can recreate this at will if you’d like me to help with debugging.@rainfallnixfig thanks for responding. I’ve raised issue #34710.
It seems php 8.0 does not allow dereferencing of numbers. The manual seems quite clear on this:
https://www.php.net/manual/en/language.references.pass.phpThis change to the woo code works here:
From
if ( function_exists( 'apache_setenv' ) ) { @apache_setenv( 'no-gzip', 1 ); // phpcs:ignore Generic.PHP.NoSilencedErrors.Discouraged, WordPress.PHP.DiscouragedPHPFunctions.runtime_configuration_apache_setenv }To:
if ( function_exists( 'apache_setenv' ) ) { $one = 1; @apache_setenv( 'no-gzip', $one ); // phpcs:ignore Generic.PHP.NoSilencedErrors.Discouraged, WordPress.PHP.DiscouragedPHPFunctions.runtime_configuration_apache_setenv }Obviously this won’t survive an upgrade so it would be good if somebody from Woo could take a look please.
I think the line
if ( function_exists( 'apache_setenv' ) ) {
returns false under php-fpm which is why we only get the problem when using the module.Hi @nawaz0705,
thanks for responding. The Apache deflate module is enabled. I have disabled gzip just for this vhost and the error no longer appears.
I don’t think disabling gzip is a long term solution though?- This reply was modified 3 years, 8 months ago by axaak.