• I received this email from you, how do I fix this error?

    Since WordPress 5.2 there is a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with this automated email.

    In this case, WordPress caught an error with your theme, Vibra.

    First, visit your website (https://djboiskoutcom.wpcomstaging.com/) and check for any visible issues. Next, visit the page where the error was caught (https://djboiskoutcom.wpcomstaging.com/wp-admin/widgets.php) and check for any visible issues.

    Please contact your host for assistance with investigating this issue further.

    If your site appears broken and you can’t access your dashboard normally, WordPress now has a special “recovery mode”. This lets you safely login to your dashboard and investigate further.

    https://djboiskoutcom.wpcomstaging.com/wp-login.php?action=enter_recovery_mode&rm_token=ESevlz2Z2fuUIUdu2kZDgS&rm_key=p9Xru6rhqAIuVZpwYSVjhM

    To keep your site safe, this link will expire in 1 day. Don’t worry about that, though: a new link will be emailed to you if the error occurs again after it expires.

    When seeking help with this issue, you may be asked for some of the following information:
    WordPress version 5.9.1
    Current theme: Vibra (version 1.2)
    Current plugin: (version )
    PHP version 7.4.28

    Error Details
    =============
    An error of type E_ERROR was caused in line 4 of the file /srv/htdocs/wp-content/themes/vibra/framework/modules/woocommerce/widgets/woocommerce-dropdown-cart/templates/content.php. Error message: Uncaught Error: Call to a member function is_empty() on null in /srv/htdocs/wp-content/themes/vibra/framework/modules/woocommerce/widgets/woocommerce-dropdown-cart/templates/content.php:4
    Stack trace:
    #0 /srv/htdocs/wp-content/themes/vibra/framework/lib/edgtf.functions.php(842): include()
    #1 /srv/htdocs/wp-content/themes/vibra/framework/lib/edgtf.functions.php(863): vibra_edge_get_template_part('framework/modul...', '', Array, false)
    #2 /srv/htdocs/wp-content/themes/vibra/framework/modules/woocommerce/widgets/woocommerce-dropdown-cart/woocommerce-dropdown-cart.php(35): vibra_edge_get_module_template_part('widgets/woocomm...', 'woocommerce')
    #3 /wordpress/core/5.9.1/wp-includes/class-wp-widget.php(393): VibraEdgeClassWoocommerceDropdownCart->widget(Array, Array)
    #4 /wordpress/core/5.9.1/wp-includes/widgets.php(2022): WP_Widget->display_callback(Array, Array)
    #5 /wordpress/core/5.9.1/wp-includes/rest-api/endpoints/class-wp-rest-widgets-controller.php(697): wp_render_widget('edgtf_woocommer...', 'cart-widget-sho...')
    #6 /wordpress/core/5.9.1/wp-includes/rest-api/endpoints/class-wp-rest-widgets-controller.php(154): WP_REST_Widgets_Controller->prepare_item_for_response(Array, Object(WP_REST_Request))
    #7 /wordpress/core/5.9.1/wp-includes/rest-api/class-wp-rest-server.php(1141): WP_REST_Widgets_Controller->get_items(Object(WP_REST_Request))
    #8 /wordpress/core/5.9.1/wp-includes/rest-api/class-wp-rest-server.php(988): WP_REST_Server->respond_to_request(Object(WP_REST_Request), '/wp/v2/widgets', Array, NULL)
    #9 /wordpress/core/5.9.1/wp-includes/rest-api.php(511): WP_REST_Server->dispatch(Object(WP_REST_Request))
    #10 /wordpress/core/5.9.1/wp-includes/rest-api.php(2860): rest_do_request(Object(WP_REST_Request))
    #11 [internal function]: rest_preload_api_request(Array, '/wp/v2/widgets?...')
    #12 /wordpress/core/5.9.1/wp-includes/block-editor.php(501): array_reduce(Array, 'rest_preload_ap...', Array)
    #13 /wordpress/core/5.9.1/wp-admin/widgets-form-blocks.php(25): block_editor_rest_api_preload(Array, Object(WP_Block_Editor_Context))
    #14 /wordpress/core/5.9.1/wp-admin/widgets.php(32): require('/wordpress/core...')
    #15 {main}
      thrown
    • This topic was modified 2 years, 9 months ago by Jan Dembowski. Reason: Moved to Fixing WordPress, this is not an Everything else WordPress topic

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

Viewing 1 replies (of 1 total)
Viewing 1 replies (of 1 total)
  • The topic ‘fatal error’ is closed to new replies.