Hi @alexdwuk,
Thanks for choosing Neve!
I don’t get any error on the single product pages from my test instances. Please provide us a screenshot with the error and the URL to your site so we can check the issue.
Thank you!
Error can be seen on this link here:
https://www.chalfamwineclub.org.uk/?product=january-2022-virtual-wine-club-flight
I have simply added the word “Test” in the “Product Short Description” field on the product. If I delete that text and leave the field blank, it all loads up perfectly!
Not had time to do much in-depth debug on this yet as been busy. However I did disable all WooCommerce related plugins and it didn’t seem to make any difference.
Hmmm looking like a Beaver Builder plugin error. Debug spits out the following:
Fatal error: Uncaught ArgumentCountError: Too few arguments to function FLBuilderCompatibility::fix_rest_excerpt_filter(), 1 passed in /home/alexdwuk/public_html/wp-includes/class-wp-hook.php on line 303 and exactly 2 expected in /home/alexdwuk/public_html/wp-content/plugins/beaver-builder-lite-version/classes/class-fl-builder-compatibility.php:1153
You need to show the whole backtrace. Beaver Builder correctly uses get_the_excerpt which has two arguments that need to be passed.
The second arg was added to the filter 6 years ago.
https://developer.ww.wp.xz.cn/reference/hooks/get_the_excerpt/
Apologies – here is the full trace:
Fatal error: Uncaught ArgumentCountError: Too few arguments to function FLBuilderCompatibility::fix_rest_excerpt_filter(), 1 passed in /home/alexdwuk/public_html/wp-includes/class-wp-hook.php on line 303 and exactly 2 expected in /home/alexdwuk/public_html/wp-content/plugins/beaver-builder-lite-version/classes/class-fl-builder-compatibility.php:1153 Stack trace: #0 /home/alexdwuk/public_html/wp-includes/class-wp-hook.php(303): FLBuilderCompatibility::fix_rest_excerpt_filter() #1 /home/alexdwuk/public_html/wp-includes/plugin.php(189): WP_Hook->apply_filters() #2 /home/alexdwuk/public_html/wp-content/plugins/twitter/src/Twitter/WordPress/Cards/Generator.php(396): apply_filters() #3 /home/alexdwuk/public_html/wp-content/plugins/twitter/src/Twitter/WordPress/Cards/Generator.php(166): Twitter\WordPress\Cards\Generator::buildPostCard() #4 /home/alexdwuk/public_html/wp-content/plugins/twitter/src/Twitter/WordPress/Head/CardsMetaElements.php(45): Twitter\WordPress\Cards\Generator::get() #5 /home/alexdwuk/public_html/wp-content/plugins/twitter/src/Twitter/WordPress/Head/CardsMetaElements.php(98): Twitter\WordPress\Head\CardsMetaElements::buildMetaElements() #6 /home/alexdwuk/public_html/wp-includes/class-wp-hook.php(301): Twitter\WordPress\Head\CardsMetaElements::outputMetaElements() #7 /home/alexdwuk/public_html/wp-includes/class-wp-hook.php(327): WP_Hook->apply_filters() #8 /home/alexdwuk/public_html/wp-includes/plugin.php(470): WP_Hook->do_action() #9 /home/alexdwuk/public_html/wp-includes/general-template.php(3015): do_action() #10 /home/alexdwuk/public_html/wp-content/themes/neve/header.php(46): wp_head() #11 /home/alexdwuk/public_html/wp-includes/template.php(770): require_once(‘/home/alexdwuk/…’) #12 /home/alexdwuk/public_html/wp-includes/template.php(716): load_template() #13 /home/alexdwuk/public_html/wp-includes/general-template.php(48): locate_template() #14 /home/alexdwuk/public_html/wp-content/plugins/woocommerce/templates/single-product.php(22): get_header() #15 /home/alexdwuk/public_html/wp-includes/template-loader.php(106): include(‘/home/alexdwuk/…’) #16 /home/alexdwuk/public_html/wp-blog-header.php(19): require_once(‘/home/alexdwuk/…’) #17 /home/alexdwuk/public_html/index.php(17): require(‘/home/alexdwuk/…’) #18 {main} thrown in /home/alexdwuk/public_html/wp-content/plugins/beaver-builder-lite-version/classes/class-fl-builder-compatibility.php on line 1153
Yea, its your “official” twitter plugin, they are aware of the bug, been aware for 2 years now and its been abandoned for 2 years too.
https://github.com/twitter/wordpress/issues/42
The fix is trivial https://github.com/twitter/wordpress/pull/43/files you might as well edit the plugin file as its never going to be updated.
Aaah amazing thank you very very much Simon 🙂
And it’s fixed. Thank you very much again for that!
Hi @alexdwuk,
We’re glad to hear the issue was solved in the meantime! It would be great if you could mark this thread as resolved.
@pross Thank you for offering your help to other community members!
Best regards to both of you!
