Banner Logo

Be a part of the family: Connect, Receive Support,
Contribute, and Reap Abundant Rewards!

Fatal Error received

Theme and Plugin Support

Viewing 4 reply threads
  • Author
    • #217111
      Adriana Webb


      I received an email on Friday and again this morning that MVX is causing a fatal error on my site.

      Here is the email, if you could please look into it.


      WordPress has 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 one of your plugins, MultiVendorX.

      First, visit your website ( and check for any visible issues. Next, visit the page where the error was caught ( 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 log in to your dashboard and investigate further.

      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 6.4.3
      Active theme: Woostify (version 2.2.8)
      Current plugin: MultiVendorX (version 4.1.2)
      PHP version 8.1.27

      Error Details
      An error of type E_ERROR was caused in line 1339 of the file /var/www/vhosts/ Error message: Uncaught TypeError: in_array(): Argument #2 ($haystack) must be of type array, null given in /var/www/vhosts/
      Stack trace:
      #0 /var/www/vhosts/ in_array()
      #1 /var/www/vhosts/ MVX_Product->convert_business_id_to_taxonomy_term_in_query()
      #2 /var/www/vhosts/ WP_Hook->apply_filters()
      #3 /var/www/vhosts/ WP_Hook->do_action()
      #4 /var/www/vhosts/ do_action_ref_array()
      #5 /var/www/vhosts/ WP_Query->get_posts()
      #6 /var/www/vhosts/ WP_Query->query()
      #7 /var/www/vhosts/ WP_Query->__construct()
      #8 /var/www/vhosts/ Automattic\WooCommerce\Blocks\Patterns\PatternsHelper::get_patterns_ai_data_post()
      #9 /var/www/vhosts/ Automattic\WooCommerce\Blocks\Patterns\PatternsHelper::get_patterns_dictionary()
      #10 /var/www/vhosts/ Automattic\WooCommerce\Blocks\BlockPatterns->register_block_patterns()
      #11 /var/www/vhosts/ WP_Hook->apply_filters()
      #12 /var/www/vhosts/ WP_Hook->do_action()
      #13 /var/www/vhosts/ do_action()
      #14 /var/www/vhosts/ require_once(‘…’)
      #15 /var/www/vhosts/ require_once(‘…’)
      #16 /var/www/vhosts/ require_once(‘…’)
      #17 /var/www/vhosts/ require_once(‘…’)
      #18 {main}

    • #217114

      Hi @Adriana Webb, Sorry to hear that you have faced an issue on your end. Kindly create a staging site that should be an exact replica of your live site and share the staging site url, temporary admin and FTP access of your site with us so that we can check the issue.

      While sharing the access don’t forget to mark your reply as private.

    • #217118
      Adriana Webb

      Creating a stage site could be a problem. My website is very big and it takes days to do and I also don’t think I have enough space to do it. Let’s give it a few days to see if any more issues or more of these emails comes up. It seems like the issue I experienced this morning has resolved itself.

    • #217135

      @Adriana Webb We’ve tried our best but we are unable to replicate the issue on our end, making it challenging to provide a fix.
      If you again get this error on your end in future please do share a temporary admin and FTP access with us so that our team can check it to identify the issue and then we will be able to provide you with a fix accordingly.
      While sharing the access don’t forget to mark your reply as private.

    • #218950

      It’s been long and we have not heard back from you. We presume your query is resolved now. We are closing this thread. If you need help or face issue in future please do create a new support ticket.

Viewing 4 reply threads

The topic ‘Fatal Error received’ is closed to new replies.