GenerateBlocks components.js TypeError after WordPress 7 update

  • Issue started immediately after updating to WordPress 7.0.

    Environment:

    * WordPress 7.0
    * GeneratePress (latest)
    * GenerateBlocks (latest)
    * GenerateBlocks Pro (latest)
    * ACF Pro (latest)

    Problem:
    In the block editor, interacting with GenerateBlocks buttons causes editor errors and blocks sometimes display “This block has encountered an error and cannot be previewed.”

    Native/core WordPress Button blocks do NOT trigger the issue.

    The issue also occurs on posts/pages that do not contain any custom ACF blocks, so this appears unrelated to custom PHP render callbacks.

    I tested:

    * clearing browser/server/CDN caches
    * updating all GeneratePress/GenerateBlocks plugins
    * newly-created GenerateBlocks buttons (not just older content)
    * posts without custom blocks

    The issue still occurs.

    Console error:

    TypeError: i is not a function
    at n (components.js?ver=%5E1.2.0:4:5549)

    The stack trace points to:

    /wp-content/plugins/generateblocks/dist/components.js?ver=%5E1.2.0

    and also loads:

    /wp-content/plugins/generateblocks-pro/dist/components.js?ver=%5E1.3.0

    This appears to be a React/editor-side issue related to GenerateBlocks components under WP 7 / React 18.

    Please let me know if there is a known compatibility issue or debugging step I should try.

  • Following up – something that is consitently causing it is changing the background color. I initially encountred it on a button, but then it also happened on a container. With the buttons I was able to change the font weight and color without it happening.

  • Hi there,

    Is it possible for you to provide a temporary admin login to the site so we can take a closer look?

    It would also be helpful if you have a staging site available, so we can safely perform debugging and testing if needed.

  • After troubleshooting further, I realized I still had SocialWarfare Pro enabled and THAT was the cause of the conflict/issues. It works fine after disabling.

  • Glad to hear that! 🙂

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