Uncaught Error (E-ERROR)

  • Resolved Enpress

    (@enpressdesign911)


    1 month ago

    Hello,

    I have received an email from WordPress that my site have an E-ERROR with the Site Kit. Here the error message below :

    檔案 /srv/htdocs/wp-content/plugins/google-site-kit/includes/loader.php 的第 43 行發生錯誤 (錯誤類型: E_ERROR)。錯誤訊息: Uncaught Error: Failed opening required ‘/srv/htdocs/wp-content/plugins/google-site-kit/includes/Core/Admin/Screen.php’ (include_path=’/:.’) in /srv/htdocs/wp-content/plugins/google-site-kit/includes/loader.php:43
    Stack trace:
    #0 /srv/htdocs/wp-content/plugins/google-site-kit/includes/Core/Admin/Screens.php(358): Google\Site_Kit\{closure}(‘Google\\Site_Kit…’)
    #1 /srv/htdocs/wp-content/plugins/google-site-kit/includes/Core/Admin/Screens.php(215): Google\Site_Kit\Core\Admin\Screens->get_screens()
    #2 /srv/htdocs/wp-content/plugins/google-site-kit/includes/Core/Admin/Screens.php(114): Google\Site_Kit\Core\Admin\Screens->add_screens()
    #3 /wordpress/core/6.6.2/wp-includes/class-wp-hook.php(324): Google\Site_Kit\Core\Admin\Screens->Google\Site_Kit\Core\Admin\{closure}(”)
    #4 /wordpress/core/6.6.2/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array)
    #5 /wordpress/core/6.6.2/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
    #6 /wordpress/core/6.6.2/wp-admin/includes/menu.php(161): do_action(‘admin_menu’, ”)
    #7 /wordpress/core/6.6.2/wp-admin/menu.php(412): require_once(‘/wordpress/core…’)
    #8 /wordpress/core/6.6.2/wp-admin/admin.php(158): require(‘/wordpress/core…’)
    #9 {main}
    thrown

    There is no issue notification about the plugin on my site health information.
    My website is still working normally, but I would like to know how this error occur.

    WordPress version: 6.6.2
    Current Theme: OceanWP 3.5.9
    Site Kit version: 1.137.0
    PHP 8.1.30

    BTW I have already updated the Site Kit to 1.138.0 after receiving the mail. Maybe the issue is fixed in this version ?

    Any help would be appreciated! Let me know if you need any additional details.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support Adam Dunnage

    (@adamdunnage)

    @enpressdesign911 Thanks for getting in touch and sharing the information you have. It sounds like you aren’t seeing any impact on your website or Site Kit, is that correct? If Site Kit is functioning without any noticeable issue then you may not need to worry about this but I’d be happy to check some things for you to ensure all is as expected.

    Please could you share your?Site Health information. You can?use this form?to share privately if preferred.?I will check to see if anything stands out from your setup and if there are any concerns. In the meantime please share any other relevant information if you have it for us which may include screenshots or recordings to show any issues you see.

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

    Thread Starter Enpress

    (@enpressdesign911)

    Hi Adam,

    Thanks for replying. Yes, there is no critical issue related to the Site Kit. I have completed the form that you provide. Please let me know if you have any feedback：）

    Plugin Support Adam Dunnage

    (@adamdunnage)

    @enpressdesign911 Thanks for sharing the information and glad to hear you don’t see any noticeable impact on your Site Kit which is reassuring.

    When checking the site health you sent, I don’t see anything of concern. I do see that you have many plugins active on your site so this could be the result of a third party plugin conflict. You could use our troubleshooting steps here to see if you could find a conflict.

    But otherwise, everything from a Site Kit perspective looks good to me. Is there anything else I can help you with at this time?

    Plugin Support Adam Dunnage

    (@adamdunnage)

    As we didn’t receive a response I’ll mark this as resolved. Feel free to?open a new support topic?if you continue to encounter issues, or reopen this topic and we’d be happy to assist.

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