Support » Plugin: Visual Composer Website Builder » There has been a critical error on this website. Please check your site admin em

  • Resolved siuwpforum

    (@siuwpforum)


    This critical error message appears whenever I select ‘Edit with Visual Composer’ to edit a page:

    “There has been a critical error on this website. Please check your site admin email inbox for instructions.
    Learn more about troubleshooting WordPress.”

    There is no error when I select ‘Classic Editor’ or ‘Gutenberg Editor’.
    The System Status in Visual Composer Settings are all shown as good.
    I receive nothing in my admin email.
    I encounter this error in the production site and create a staging site to try things out and the same error appears. The ‘Link to the page’ posted above is on the staging site.

    Thank you for your help!

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

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Rohan Khandeparkar

    (@rohanvc)

    Hi,

    Please activate the WordPress debug mode at your end. Once done, check the page where critical error message is displayed. This will display the error message and it’s location. You can share it’s screenshot with us to check it further.

    Thread Starter siuwpforum

    (@siuwpforum)

    Thank you for your reply.

    I installed 3 plugins to help with debugging:
    1) WP Debugging, 2) Debug Bar, 3) Query Monitor

    On the All Pages screen, I hit the ‘Add New with Visual Composer’ button and the following info appeared:

    Fatal error: Uncaught Error: Argument 1 passed to GoDaddy\WordPress\MWC\Common\Content\Context\Screen::setPageId() must be of the type string, null given, called in /var/www/wp-content/mu-plugins/gd-system-plugin/plugins/mwc-core/vendor/godaddy/mwc-common/src/Traits/CanBulkAssignPropertiesTrait.php on line 31
    in /var/www/wp-content/mu-plugins/gd-system-plugin/plugins/mwc-core/vendor/godaddy/mwc-common/src/Content/Context/Screen.php on line 134

    Call stack:

    GoDaddy\W\M\C\C\C\Screen::setPageId()
    wp-content/mu-plugins/gd-system-plugin/plugins/mwc-core/vendor/godaddy/mwc-common/src/Traits/CanBulkAssignPropertiesTrait.php:31
    GoDaddy\W\M\C\C\C\Screen::setProperties()
    wp-content/mu-plugins/gd-system-plugin/plugins/mwc-core/vendor/godaddy/mwc-common/src/Content/Context/Screen.php:62
    GoDaddy\W\M\C\C\C\Screen::__construct()
    wp-content/mu-plugins/gd-system-plugin/plugins/mwc-core/vendor/godaddy/mwc-common/src/Repositories/WordPressRepository.php:320
    GoDaddy\W\M\C\R\WordPressRepository::getCurrentScreen()
    wp-content/mu-plugins/gd-system-plugin/plugins/mwc-core/src/Client/Client.php:252
    GoDaddy\W\M\C\C\Client::getPageContextVariables()
    wp-content/mu-plugins/gd-system-plugin/plugins/mwc-core/src/Client/Client.php:223
    GoDaddy\W\M\C\C\Client::getInlineScriptVariables()
    wp-content/mu-plugins/gd-system-plugin/plugins/mwc-core/src/Client/Client.php:202
    GoDaddy\W\M\C\C\Client::enqueueApp()
    wp-content/mu-plugins/gd-system-plugin/plugins/mwc-core/src/Client/Client.php:184
    GoDaddy\W\M\C\C\Client::enqueueAssets()
    wp-includes/class-wp-hook.php:303
    WP_Hook::apply_filters()
    wp-includes/class-wp-hook.php:327
    WP_Hook::do_action()
    wp-includes/plugin.php:470
    do_action()
    wp-content/plugins/visualcomposer/visualcomposer/resources/views/editor/frontend/frontend.php:38
    include()
    wp-content/plugins/visualcomposer/visualcomposer/Helpers/Views.php:56
    VisualComposer\H\Views::render()
    wp-content/plugins/visualcomposer/visualcomposer/Modules/Editors/Frontend/Controller.php:150

    Notice: Undefined index: file in /var/www/wp-content/plugins/query-monitor/collectors/php_errors.php on line 286

    Notice: Undefined index: line in /var/www/wp-content/plugins/query-monitor/collectors/php_errors.php on line 286
    VisualComposer\M\E\F\Controller::renderEditorBase()
    ReflectionMethod::invokeArgs()
    wp-content/plugins/visualcomposer/visualcomposer/Framework/Container.php:63
    VisualComposer\F\Container::call()
    wp-content/plugins/visualcomposer/visualcomposer/Helpers/Traits/EventsFilters.php:30
    VisualComposer\M\E\F\Controller::VisualComposer\H\T\{closure}()
    wp-content/plugins/visualcomposer/visualcomposer/Framework/Illuminate/Container/Container.php:260
    VisualComposer\F\I\C\Container::call()
    wp-content/plugins/visualcomposer/visualcomposer/Framework/Illuminate/Filters/Dispatcher.php:36
    VisualComposer\F\I\F\Dispatcher::fire()
    wp-content/plugins/visualcomposer/visualcomposer/Framework/helpers.php:74
    vcfilter()
    wp-content/plugins/visualcomposer/visualcomposer/Modules/Editors/Frontend/Controller.php:93

    Notice: Undefined index: file in /var/www/wp-content/plugins/query-monitor/collectors/php_errors.php on line 286

    Notice: Undefined index: line in /var/www/wp-content/plugins/query-monitor/collectors/php_errors.php on line 286
    VisualComposer\M\E\F\Controller::init()
    ReflectionMethod::invokeArgs()
    wp-content/plugins/visualcomposer/visualcomposer/Framework/Container.php:63
    VisualComposer\F\Container::call()
    wp-content/plugins/visualcomposer/visualcomposer/Modules/Editors/Frontend/Controller.php:45
    VisualComposer\M\E\F\Controller::VisualComposer\M\E\F\{closure}()
    wp-content/plugins/visualcomposer/visualcomposer/Framework/Container.php:67
    VisualComposer\F\Container::call()
    wp-content/plugins/visualcomposer/visualcomposer/Helpers/Traits/WpFiltersActions.php:23
    VisualComposer\M\E\F\Controller::VisualComposer\H\T\{closure}()
    wp-includes/class-wp-hook.php:303
    WP_Hook::apply_filters()
    wp-includes/plugin.php:189
    apply_filters()
    wp-includes/pluggable.php:1099
    auth_redirect()
    wp-admin/admin.php:99
    require_once()
    wp-admin/post-new.php:10

    Plugin Support Rohan Khandeparkar

    (@rohanvc)

    Thanks for sharing. The fatal error is arising from the system plugin of godaddy hosting. You can see the error message pointing to their plugin: https://i.imgur.com/MBbZDaI.png
    I can recommend you to contact the godaddy support and share the error message with them, so that they can guide you further. If they need any details from our end, we will be glad to share it with them.

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.