Woke up to errors and a non-compliant dashboard…

  • Unknown's avatar
    rennenpro · Member ·

    Hello,

    I woke up to this error message this morning:
    Metadata_Registry::register_collection was called incorrectly. Block metadata collections can only be registered for a specific plugin. The provided path is neither a core path nor a valid plugin path. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /wordpress/core/6.7/wp-includes/functions.php on line 6114

    The only changes I made yesterday was adding a new product and changing the homepage to include a link to it, on a button.

    Secondly, on my dashboard im confronted with this message:

    Jetpack can’t communicate with your site because the REST API is not responding correctly.

    • I cant download, delete or deactivate plugins
    • My menu is run by the plugin “elementor header & footber builder” but clicking on any menu option leads to a “page not found” page

    I have a debugging plugin and it shows this information:

    Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 158435536 bytes) in /srv/htdocs/wp-content/plugins/wp-debugging/vendor/norcross/debug-quick-look/includes/handler.php on line 252

    Total log entries: 0× Purge File/srv/htdocs/wp-content/debug.log

    There has been a critical error on this website. Please check your site admin email inbox for instructions. If you continue to have problems, please try the support forums.

    Any support would be really helpful. Ive no idea where to go from here!

    Thank you

    The blog I need help with is: (visible only to logged in users)

  • Unknown's avatar
    rennenpro · Member ·

    Furthermore, I am unable to essentially do anything.
    I am unable to edit a product, edit a page, upload images, click links, etc.

    Dashboard just throws up an error message every time I try to do anything

  • Unknown's avatar
    rennenpro · Member ·

    I have done a restore to 2 days ago and still receive the same error message

  • Unknown's avatar
    ngfangkiang · Member ·

    Hello,

    Can you share more information about the Metadata_Registry errors using the query monitor plugin?

    The current debug information does not show enough information to find the actual cause, as it points to the function wp_trigger_error() at lines 6075 – 6116.

    function wp_trigger_error( $function_name, $message, $error_level = E_USER_NOTICE ) {

....

}

    For JetPack issues, you can follow the instructions to restore the JetPack connection.

    Regarding “Fatal error: Allowed memory size of 536870912 bytes exhausted”. I think you should try to increase the PHP memory limit. You can increase the PHP memory limit by editing your wp-config.php file.

    The code should look like the following.

    define('WP_MEMORY_LIMIT', '256M');

    If it is still not enough, you can increase it to 512M depending on the server.

    define('WP_MEMORY_LIMIT', '512M');

  • Unknown's avatar
    ngfangkiang · Member ·

    In case you need to restore your site quickly, I recommend rolling back to a previous WordPress core version (6.6.2). https://wordpress.org/plugins/core-rollback/

  • Unknown's avatar
    rennenpro · Member ·

    Hello,

    Thank you for the response. Yesterday, I tried multiple restores further and further back to no avail. Then I downloaded a .zip plugin and installed it via uploading. For whatever reason, it cleared the main error but the jetpack error remains.


    However, I do not want to be in that position again.

    Heres a few screenshots of what query monitor pulls up

    Also:

    • I have disabled the stripe payments plugin – but I need this?
    • I am unable to acces file editor due to errors shown on the screen… it doesnt allow me to scroll down. See last image.

    Jetpack states I need to activate Legacy rest API. When I activate legacy rest api I am prompted to deacivate it because of compatibility issues. What is this paradox WP have created? Both jetpack and legacy rest api came pre installed. What is the solution?

    Thank you


  • Unknown's avatar
    rennenpro · Member ·

    Incase youre unable to read:
    Doing it wrong:

    Function register_sidebar was called incorrectly. No id was set in the arguments array for the “Sidebar 1” sidebar. Defaulting to “sidebar-1”. Manually set the id to “sidebar-1” to silence this notice and keep existing sidebar content. (This message was added in version 4.2.0.)+

    1. register_sidebar()

    Plugin: code-snippetsFunction WP_Block_Metadata_Registry::register_collection was called incorrectly. Block metadata collections can only be registered for a specific plugin. The provided path is neither a core path nor a valid plugin path. (This message was added in version 6.7.0.)-

    1. WP_Block_Metadata_Registry::register_collection()
      wp-includes/class-wp-block-metadata-registry.php:117
    2. wp_register_block_metadata_collection()
      wp-includes/blocks.php:391
    3. Jetpack_Gutenberg::register_block_metadata_collection()
      /wordpress/plugins/jetpack/14.1-a.1/class.jetpack-gutenberg.php:1356
    4. do_action('plugins_loaded')
      wp-includes/plugin.php:517

    WordPress Core

  • Unknown's avatar
    rennenpro · Member ·

    …..and the error is back again without me doing anything…..

  • Unknown's avatar
    ngfangkiang · Member ·

    Hi, thanks for your reply.

    Answer 1: I have disabled the stripe payments plugin – but I need this?

    You don’t need to disable the Stripe payments plugin. From the screenshot above, this is just a deprecation notice reminding developers to upgrade the code before it is deprecated in the next version of PHP or WordPress core. You can ignore these because these are the way developers keep track of their code to make sure they follow the latest PHP standards.

    Answer 2: I am unable to acces file editor due to errors shown on the screen… it doesnt allow me to scroll down. See last image.

    The reason you are receiving the passing null to parameters is that you are using PHP 8.1 and above. Since PHP 8.1, they implement strict rules that require us to write default values on our function. Before PHP 8, it was not required.

    You don’t need to do anything as it serves as a reference for developers to keep their code compliant with the latest PHP standards. It’s just a deprecation notice for developers to make sure their code is written in the latest PHP standards.

    You can fix this by disabling the debug tools and the debug settings in wp-config.php.

    Answer 3: Incase youre unable to read: Doing it wrong: (Query Monitor)

    Query Monitor is a development tool, and as a website owner, I recommend that you only focus on errors highlighted in red, such as fatal errors. The rest is for developers only.

    Doing it wrong: Code Snippets

    The first line reported is due to the Code Snippets plugin. I recommend you report it to the plugin developer.


    Doing it wrong: WordPress Core

    I believe the WordPress core team is aware of this issue and they probably will fix it in WordPress 6.7.1.

    Overall, your website looks good at the moment, and I didn’t notice any serious errors that you would need to fix on your own. You can now turn off all debugging tools, including settings you may have modified on wp-config.php. After this, you will be able to use the editor perfectly.

    I hope this helps. If you need any further assistance, please feel free to let me know.

  • The topic ‘Woke up to errors and a non-compliant dashboard…’ is closed to new replies.