Numerous block errors on 3.0.0 update

  • Resolved Derek Rippe

    (@dwrippe)


    1 year, 7 months ago

    Hi there,

    I’m seeing a large number of error notices after updating to 3.0.0 (on dozens of sites I manage). They all look like:

    Your site doesn’t include support for the "genesis-blocks/gb-columns" block. You can leave this block intact, convert its content to a Custom HTML block, or remove it entirely.

    I’m seeing it for the following blocks:

    • genesis-blocks/gb-columns
    • genesis-blocks/gb-accordion
    • genesis-blocks/gb-post-grid

    There may be others, as I haven’t checked all of the Genesis Blocks (those are three I just happen to use regularly).

    In addition, those blocks no longer show up when attempting to insert blocks.

    This is causing some pretty major issues on my end, as it’s making some page layouts extremely difficult to edit, if not destructive should a user decide to convert it to HTML.

    • This topic was modified 1 year, 7 months ago by Derek Rippe.
Viewing 14 replies - 1 through 14 (of 14 total)
  • Plugin Contributor Phil Johnston

    (@johnstonphilip)

    Hey Derek,

    Sorry to hear this is happening! Just to double check, those errors typically appear if the plugin gets deactivated. Sometimes (though rarely) this can happen as part of an update in WordPress. Can we rule that out?

    I’ve just tested this on a fresh installation with no other plugins, and I’m not seeing these errors.

    Thread Starter Derek Rippe

    (@dwrippe)

    Hi Phil,

    Plugin definitely isn’t deactivated. All sites are running the latest version of WP (6.2.2), along with a handful of other plugins (naturally). I’ve got a couple of staging sites I could temporarily connect you with to view the issue first-hand, if that helps? We’d have to connect via some other platform…

    Plugin Contributor Ryan Kienstra

    (@ryankienstra)

    Hi @dwrippe,

    Thanks, that helps. Are there any Genesis Blocks in the block inserter?

    Thread Starter Derek Rippe

    (@dwrippe)

    Hi @ryankienstra,

    There are not, which is really strange. But if I rollback to 2.0.0, everything works per usual.

    Plugin Contributor Ryan Kienstra

    (@ryankienstra)

    Thanks, @dwrippe. Does the browser have any JS console errors?

    Thread Starter Derek Rippe

    (@dwrippe)

    A couple, yep:

    • [Error] SyntaxError: Invalid regular expression: invalid group specifier name – (anonymous function) (blocks.build.js:1)
    • [Error] Failed to load resource: the server responded with a status of 404 () (default.editor.min.js.map, line 0)
    • [Error] Failed to load resource: the server responded with a status of 500 () (google_photos, line 0)
    • This reply was modified 1 year, 7 months ago by Derek Rippe.
    Plugin Contributor Ryan Kienstra

    (@ryankienstra)

    Thanks, the first error is probably the problem.

    1. What browser is this on?
    2. Do you see this in multiple browsers?
    Thread Starter Derek Rippe

    (@dwrippe)

    Ahh, good call! This is only happening in Safari (Version 15.0).

    I also checked it in Chrome, Firefox, Firefox Developer and Brave, with no issue.

    Glad to hear it’s either just on my end, or just for Safari users. Of course, it makes me wonder why it’s only happening in Safari…

    Plugin Contributor Ryan Kienstra

    (@ryankienstra)

    Hi @dwrippe,

    Thanks, that helps a lot! Would you be able to upgrade to Safari 16.4?

    I’m not seeing that error on Safari 16.4, but maybe you’re happy using another browser instead.

    Plugin Contributor Ryan Kienstra

    (@ryankienstra)

    If it’s alright, I’m marking this as resolved, but let’s keep the conversation going here.

    Thread Starter Derek Rippe

    (@dwrippe)

    @ryankienstra definitely. I’ll be back in the office this evening and will update Safari (not sure why it hasn’t auto-updated, as it sounds like I’m behind a full version).

    Plugin Contributor Ryan Kienstra

    (@ryankienstra)

    Thanks, Derek! Looking forward to hearing how it goes.

    Thread Starter Derek Rippe

    (@dwrippe)

    Indeed – was an out-of-date Safari issue. I had no idea I was so far behind, haha. Upgraded to 16.6 and all issues are gone.

    Thanks for your help @ryankienstra and @johnstonphilip!

    Plugin Contributor Ryan Kienstra

    (@ryankienstra)

    Hi @dwrippe,

    Great to hear! Thanks a lot for working through this.

Viewing 14 replies - 1 through 14 (of 14 total)
  • The topic ‘Numerous block errors on 3.0.0 update’ is closed to new replies.