Title: Plugin triggers errors unregistered blocks
Last modified: January 18, 2023

---

# Plugin triggers errors unregistered blocks

 *  Resolved [Philipp Bammes](https://wordpress.org/support/users/tyrannous/)
 * (@tyrannous)
 * [3 years, 4 months ago](https://wordpress.org/support/topic/plugin-triggers-errors-unregistered-blocks/)
 * On projects that deactivated blocks with `[unregister_block_type()](https://developer.wordpress.org/reference/functions/unregister_block_type/)`(
   or the JS equivalent `unregisterBlockType()`), the HubSpot plugin triggers error
   messages in the browser console when editing a post:
 *     ```wp-block-code
       gutenberg.js?ver=10.0.16:1 Block "core/comments-query-loop" is not registered.
       gutenberg.js?ver=10.0.16:1
       gutenberg.js?ver=10.0.16:1 Block "core/post-comments" is not registered.
       ```
   
 * Please check for the existence of blocks before using them. Thanks!
 * Also, the plugin triggers errors for blocks and plugins like this:
 *     ```wp-block-code
       gutenberg.js?ver=10.0.16:1 Plugin "[redacted-custom-plugin-name]" is already registered.
       gutenberg.js?ver=10.0.16:1 Block "[redacted-custom-block-name]" is already registered.
       ```
   
 * Could you please have a look if these two types of error logs can be prevented?
   Thanks!

Viewing 4 replies - 1 through 4 (of 4 total)

 *  [harthur90](https://wordpress.org/support/users/harthur90/)
 * (@harthur90)
 * [3 years, 4 months ago](https://wordpress.org/support/topic/plugin-triggers-errors-unregistered-blocks/#post-16384547)
 * Hi [@tyrannous](https://wordpress.org/support/users/tyrannous/) Thanks for your
   message. I’ll try to replicate and let you know once a fix is available! If you
   could send an email with your list of plugins and configuration (WP version, 
   php version) to [wordpress-support-groups@hubspot.com](https://wordpress.org/support/topic/plugin-triggers-errors-unregistered-blocks/wordpress-support-groups@hubspot.com?output_format=md)
   this would help the process
   Thanks in advanceBest regards
 *  Thread Starter [Philipp Bammes](https://wordpress.org/support/users/tyrannous/)
 * (@tyrannous)
 * [3 years, 4 months ago](https://wordpress.org/support/topic/plugin-triggers-errors-unregistered-blocks/#post-16384841)
 * Hi [@harthur90](https://wordpress.org/support/users/harthur90/), thanks for getting
   back to me so quickly.
 * I noticed that basically all error messages, even from other plugins, originated
   from `https://example.com/wp-content/plugins/leadin/build/gutenberg.js`. Therefore,
   I deactivated the Hubspot plugin for testing purposes and noticed that the errors
   are still present, but this time coming from the block editor itself.
 * Apparently, there is some kind of proxying happening from the block editor to`
   gutenberg.js`.
 * Unfortunately, there’s no source version of that file available publicly online.
   The messages are proxyied here:
 *     ```wp-block-code
       // […]
       "assert" === t ? !1 === e[0] && (i = "Assertion failed: " + (e.slice(1).join(" ") || "console.assert"),
                                   s.extra.arguments = e.slice(1),
                                   r && r(i, s)) : r && r(i, s),
                                   n && Function.prototype.apply.call(n, a, e) // <-- here
       // […]
       ```
   
 * Closing this, as the error messages are unrelated to the HubSpot plugin. Still,
   it would be great if you could check if this “proxying” is necessary because 
   it’s pretty confusing and can potentially cause false alerts like this one.
 * Thanks!
   Philipp
 *  Thread Starter [Philipp Bammes](https://wordpress.org/support/users/tyrannous/)
 * (@tyrannous)
 * [3 years, 4 months ago](https://wordpress.org/support/topic/plugin-triggers-errors-unregistered-blocks/#post-16384863)
 * Hi [@harthur90](https://wordpress.org/support/users/harthur90/), sorry for misusing
   this thread for something unrelated; it would be great if you could look at [https://wordpress.org/support/topic/make-old-plugin-versions-available/](https://wordpress.org/support/topic/make-old-plugin-versions-available/).
 * You are currently not using SVN tags which can cause significant issues in Comoser-
   based projects. Please refer to a similar support thread of a different plugin
   for a detailed explanation of the problem: [https://wordpress.org/support/topic/adopt-the-use-of-release-tags/#post-15516073](https://wordpress.org/support/topic/adopt-the-use-of-release-tags/#post-15516073)
 * Thanks!
 *  [harthur90](https://wordpress.org/support/users/harthur90/)
 * (@harthur90)
 * [3 years, 4 months ago](https://wordpress.org/support/topic/plugin-triggers-errors-unregistered-blocks/#post-16384875)
 * [@tyrannous](https://wordpress.org/support/users/tyrannous/) Thanks for closing
   the support thread. We do have plans to support the use of SVN tags. This should
   be done as part of our quarter priorities. If you do wish for a particular plugin
   version you can request them via email 🙂
 * Best Regards

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Plugin triggers errors unregistered blocks’ is closed to new replies.

 * ![](https://ps.w.org/leadin/assets/icon-256x256.png?rev=3041936)
 * [HubSpot All-In-One Marketing - Forms, Popups, Live Chat](https://wordpress.org/plugins/leadin/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/leadin/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/leadin/)
 * [Active Topics](https://wordpress.org/support/plugin/leadin/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/leadin/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/leadin/reviews/)

## Tags

 * [gutenberg](https://wordpress.org/support/topic-tag/gutenberg/)

 * 4 replies
 * 2 participants
 * Last reply from: [harthur90](https://wordpress.org/support/users/harthur90/)
 * Last activity: [3 years, 4 months ago](https://wordpress.org/support/topic/plugin-triggers-errors-unregistered-blocks/#post-16384875)
 * Status: resolved