Home>Support>Site Origin Widget Bundle – Critical Error

Site Origin Widget Bundle – Critical Error

By BLU Medic, 1 year ago. Last reply by BLU Medic, 1 year ago.

Hello,

I am getting the following error on my website:

There has been a critical error on this website. Please check your site admin email inbox for instructions.

Learn more about troubleshooting WordPress.

The error appears across the website at almost random, only affecting various pages (dashboard, updates page, various pages and posts). Sometimes the error goes away after a refresh, but often the error will constantly pop up.

The error disappears when I disable the SiteOrigin Widgets Bundle plugin. I have not received any emails in my admin email inbox and the learn more link isn’t helpful.

Thank you in advance.

This is our free support forum. Replies can take several days. If you need fast email support, please purchase a SiteOrigin Premium license.

  1. 1 year, 5 months ago Andrew Misplon
    Hi, I Work Here

    Hi, thanks for getting in touch.

    Are you able to enable debugging to find out the error details? The process involves accessing your server via FTP or your hosting control panel (Hosting File Manager).

    https://wordpress.org/documentation/article/debugging-in-wordpress/

  2. 1 year, 5 months ago Andrew Misplon
    Hi, I Work Here

    Alternatively, an easy first step might be to download the plugin ZIP file from https://wordpress.org/plugins/so-widgets-bundle/. Go to PluginsAdd NewUpload Plugin and install the ZIP file manually. Overwrite the existing plugin when prompted.

  3. 1 year, 5 months ago BLU Medic

    I have uploaded the plugin but it hasn’t made any difference.

    I enabled debug mode and it has produced the following:

    Deprecated: Optional parameter $name declared before required parameter $combination is implicitly treated as a required parameter in /home3/shieldsd/public_html/tsub/wp-content/plugins/wpc-custom-related-products/wpc-custom-related-products.php on line 382

Deprecated: Optional parameter $keyType declared before required parameter $notAfter is implicitly treated as a required parameter in /home3/shieldsd/public_html/tsub/wp-content/plugins/ssl-zen/ssl_zen/lib/LEOrder.php on line 77

Deprecated: Return type of Requests_Cookie_Jar::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home3/shieldsd/public_html/tsub/wp-includes/Requests/Cookie/Jar.php on line 63

Deprecated: Return type of Requests_Cookie_Jar::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home3/shieldsd/public_html/tsub/wp-includes/Requests/Cookie/Jar.php on line 73

Deprecated: Return type of Requests_Cookie_Jar::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home3/shieldsd/public_html/tsub/wp-includes/Requests/Cookie/Jar.php on line 89

Deprecated: Return type of Requests_Cookie_Jar::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home3/shieldsd/public_html/tsub/wp-includes/Requests/Cookie/Jar.php on line 102

Deprecated: Return type of Requests_Cookie_Jar::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home3/shieldsd/public_html/tsub/wp-includes/Requests/Cookie/Jar.php on line 111

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home3/shieldsd/public_html/tsub/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 40

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home3/shieldsd/public_html/tsub/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 51

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home3/shieldsd/public_html/tsub/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 68

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home3/shieldsd/public_html/tsub/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 82

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home3/shieldsd/public_html/tsub/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 91

Fatal error: Out of memory (allocated 20971520) (tried to allocate 655360 bytes) in /home3/shieldsd/public_html/tsub/wp-content/plugins/woocommerce/includes/class-wc-countries.php on line 169

There has been a critical error on this website. Please check your site admin email inbox for instructions.

Learn more about troubleshooting WordPress.

    Thank you

  4. 1 year, 5 months ago Andrew Misplon
    Hi, I Work Here

    Thanks, the fatal error is at the end of the output. Please, see https://www.wpbeginner.com/wp-tutorials/fix-wordpress-memory-exhausted-error-increase-php-memory/.

  5. 1 year, 5 months ago BLU Medic

    Hello,
    I have increased the memory limit to 256MB and the error is still there.
    Thank you

  6. 1 year, 5 months ago Andrew Misplon
    Hi, I Work Here

    You can try installing https://wordpress.org/plugins/server-ip-memory-usage/ to see if your server and WP memory limits have increased. You can also consult the debug.log file again to see what the error is that’s persisting. The deprecated notices aren’t relevant, only lines reading fatal error.

  7. 1 year, 5 months ago BLU Medic

    Hello,

    This is what that plugin has given me:

    | Memory: 22 of 512 MB (4%) | WP LIMIT: 256 MB | IP 143.95.233.90 (reseller45.webserversystems.com) | PHP 8.1.17 @64BitOS

    Thank you

  8. 1 year, 5 months ago Andrew Misplon
    Hi, I Work Here

    That looks fine. You can go back to the error log to see what’s happening. In the above log provided, WooCommerce is triggering the issue.

  9. 1 year, 5 months ago BLU Medic

    Hello,

    I have deactivated Woocommerce and am now getting a new error:

    Fatal error: Out of memory (allocated 12582912) (tried to allocate 20480 bytes) in /home3/shieldsd/public_html/tsub/wp-content/plugins/so-widgets-bundle/icons/fontawesome/filter.php on line 5

    Thank you

  10. 1 year, 5 months ago Andrew Misplon
    Hi, I Work Here

    Thanks for the update. It’s hard to say what the cause of the issue is. You can try establishing a working baseline as follows:

    – Temporarily switch to a default theme like Twenty Nineteen.
    – Temporarily deactivate all plugins except for the Widgets Bundle.
    – Confirm a working baseline in the above position.
    – Reactivate your theme and re-test.
    – Reactivate your plugins one by one and re-test.
    – When the issue re-occurs, deactivate all plugins except for the Widgets Bundle and the last plugin activation that triggered the issue to confirm.

  11. 1 year, 5 months ago BLU Medic

    I’ve tried deactivating and the issue does seem to be in Woocommerce. Thank you for the help.

  12. 1 year, 5 months ago Andrew Misplon
    Hi, I Work Here

    You’re welcome. Hopefully, you’re able to make headway soon. Cheers for now.

  13. 1 year, 5 months ago BLU Medic

    Thank you

Replies on this thread are closed. Please create a new thread if you have a question, or purchase a SiteOrigin Premium license if you need one-on-one email support.

Get The Most Out of SiteOrigin with SiteOrigin Premium

Find Out More