CRITICAL Uncaught Error

  • Resolved tuomonurkkala

    (@tuomonurkkala)


    1 year, 6 months ago

    Hi there,

    I am having some problems with your plugin. These are from my WooCommerce logs:

    2023-08-29T20:48:47+00:00 CRITICAL Uncaught Error: Failed opening required ‘/home2/sukkianet/public_html/wp-content/plugins/google-site-kit/includes/Core/Util/BC_Functions.php’ (include_path=’.:/opt/alt/php80/usr/share/pear:/opt/alt/php80/usr/share/php:/usr/share/pear:/usr/share/php’) in /home2/sukkianet/public_html/wp-content/plugins/google-site-kit/includes/loader.php:43 Stack trace: #0 /home2/sukkianet/public_html/wp-content/plugins/google-site-kit/includes/Modules/Tag_Manager/Web_Tag.php(78): Google\Site_Kit\{closure}() #1 /home2/sukkianet/public_html/wp-content/plugins/google-site-kit/includes/Core/Util/Method_Proxy_Trait.php(25): Google\Site_Kit\Modules\Tag_Manager\Web_Tag->render() #2 /home2/sukkianet/public_html/wp-includes/class-wp-hook.php(310): Google\Site_Kit\Modules\Tag_Manager\Web_Tag->Google\Site_Kit\Core\Util\{closure}() #3 /home2/sukkianet/public_html/wp-includes/class-wp-hook.php(334): WP_Hook->apply_filters() #4 /home2/sukkianet/public_html/wp-includes/plugin.php(517): WP_Hook->do_action() #5 /home2/sukkianet/public_html/wp-includes/general-template.php(3053): do_action() #6 /home2/sukkianet/public_html/wp-content/themes/basel/header.php(13): wp_head() #7 /home2/sukkianet/public_html/wp-includes/template.php(785): require_once(‘/home2/sukkiane…’) #8 /home2/sukkianet/public_html/wp-includes/template.php(720): load_template() #9 /home2/sukkianet/public_html/wp-includes/general-template.php(48): locate_template() #10 /home2/sukkianet/public_html/wp-content/themes/basel/woocommerce/archive-product.php(26): get_header() #11 /home2/sukkianet/public_html/wp-content/plugins/woocommerce/includes/wc-core-functions.php(345): include(‘/home2/sukkiane…’) #12 /home2/sukkianet/public_html/wp-content/plugins/woocommerce/templates/taxonomy-product-attribute.php(22): wc_get_template() #13 /home2/sukkianet/public_html/wp-includes/template-loader.php(106): include(‘/home2/sukkiane…’) #14 /home2/sukkianet/public_html/wp-blog-header.php(19): require_once(‘/home2/sukkiane…’) #15 /home2/sukkianet/public_html/index.php(17): require(‘/home2/sukkiane…’) #16 {main} thrown t?ss? /home2/sukkianet/public_html/wp-content/plugins/google-site-kit/includes/loader.php rivill? 43

    Best Regards,

    Tuomo Nurkkala

    The page I need help with: [log in to see the link]

Viewing 11 replies - 1 through 11 (of 11 total)
  • Plugin Support James Osborne

    (@jamesosborne)

    Thanks for reaching out @tuomonurkkala. So we can determine more on this, please share the following:

    1. Your Site Health information. You can use this form to share privately if preferred.??
    2. Does this impact any Site Kit functionality, or can you confirm that the plugin dashboard and any WooCommerce pages function as expected?

    Let me know if you have any questions with the above.

    Thread Starter tuomonurkkala

    (@tuomonurkkala)

    Hi @jamesosborne

    1. Okay, I have sent this privately.
    2. I am having problems getting my conversions to Site kit. It is showing my conversions in Google Ads ([b69f] Google Listings and Ads purchase action), but not in Analytics and Site kit. The conversions are linked with Tag manager as well. :/ All other parts works just fine.
    Plugin Support James Osborne

    (@jamesosborne)

    Thanks for the update @tuomonurkkala. As I didn’t notice anything unusual with your current setup, can you share whether the Site Kit dashboard works as expected which I check this with the team? I mention this as the error may only exist within your WooCommerce logs, without any impact on Site Kit functionality.

    In relation to your conversions mention, we’re limited to Site Kit queries here in the plugin support forums. While Site Kit doesn’t have any conversion tracking features, you can use the Tag Manager Help Center, where the product experts can assist with any conversion related queries.

    I’ll report back to you here once I check the specific WooCommerce error you reported with the team.

    Thread Starter tuomonurkkala

    (@tuomonurkkala)

    Hi @jamesosborne

    Everything looks fine in the Site Kit dashboard. I only found that error from the WooCommerce Logs and that Log is from yesterday. I updated WooCommerce today so maybe there was some problems with your plugin.

    Okay, thanks! I will contact them. ??

    Best Regards,

    Tuomo Nurkkala

    Plugin Support James Osborne

    (@jamesosborne)

    Appreciate the update @tuomonurkkala. I’ll check this error with the team and report back to you here. The Stack trace along with the error you provided may indeed indicate something that can be addressed.

    Thread Starter tuomonurkkala

    (@tuomonurkkala)

    Thank you @jamesosborne !

    Plugin Support James Osborne

    (@jamesosborne)

    @tuomonurkkala After discussing this with the team it’s possible that you encountered this error based on a plugin update not completing in full. Can you try to uninstall the plugin and install once more, checking does the same occur after doing so?

    Thread Starter tuomonurkkala

    (@tuomonurkkala)

    Is there a possibility @jamesosborne to get the newest update in ZIP file? If I would try to update it that way.

    Plugin Support James Osborne

    (@jamesosborne)

    You can download the last version via this link @tuomonurkkala, version 1.108.0 at time of writing.

    Let me know how you get on after updating, or ask if you have any questions.

    Thread Starter tuomonurkkala

    (@tuomonurkkala)

    Hi @jamesosborne

    I ran the update yesterday and I’m not getting any error logs of your plugin. ??

    Best Regards,

    Tuomo Nurkkala

    Plugin Support James Osborne

    (@jamesosborne)

    Great to know, and thank you for sharing this update. If you run into any further issues be sure to reach out. If you have a moment free please also consider leaving a review.?

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘CRITICAL Uncaught Error’ is closed to new replies.