Support » Plugin: Atomic Blocks - Gutenberg Blocks Collection » Whitescreen an JS exception when editing site

  • Resolved paddy3001

    (@paddy3001)


    Hi,

    lately when I want to edit a certain site using the Atomic Blocks theme and plugin I get a whitescreen. The console gives me the following JS exception:

    blocks.min.js?ver=6.0.6:2 Block validation: Block validation failed for atomic-blocks/ab-cta ({name: “atomic-blocks/ab-cta”, title: “AB Call To Action”, description: “Add a call to action section with a title, text, and a button.”, icon: {…}, category: “atomic-blocks”, …}

    It further on shows me what the expected and the actual output was. The only difference is, that the button link on the call to action block contains a rel=”noopener noreferrer” on the actual output which does not seem to be expected by the Plugin.

    Is there a workaround or is it a little bug that can be fixed? The issue started after the update to WordPress 5.1.

    Thanks for your help!

Viewing 14 replies - 1 through 14 (of 14 total)
  • Hi

    I have exactly the same problem, with that cta block and after update to 5.1

    Thanks

    • This reply was modified 8 months, 4 weeks ago by Sergixnet.
    • This reply was modified 8 months, 4 weeks ago by Sergixnet.
    Plugin Author atomicblocks

    (@atomicblocks)

    Hi folks,

    The update that included the noreferrer code happened about two months ago. The latest version of the plugin should update that block. Have you made sure you have the latest Atomic Blocks installed? You’ll be looking for version 1.5.2.

    Hi!

    Yes I have the latest update installed and running (Version 1.5.2).

    Thanks for your help!

    I still get the error “This block contains unexpected or invalid content” with a fresh made CTA-block on version 1.5.2 on WordPress 5.1.
    <div style="text-align:center" class="wp-block-atomic-blocks-ab-cta ab-block-cta"><div class="ab-cta-content"><h2 class="ab-cta-title ab-font-size-32" style="color:#32373c">Call to Action</h2><div class="ab-cta-text ab-font-size-32" style="color:#32373c"><p>call to action test</p></div></div><div class="ab-cta-button"><a href="https://www.gva.be" target="_self" class="ab-button ab-button-shape-rounded ab-button-size-medium" style="color:#ffffff;background-color:#3373dc" rel="noopener noreferrer">read more</a></div></div>

    Same as above on 1.5.2 since upgrade to 5.1

    Plugin Author John Parris

    (@mindctrl)

    Hi everyone,

    We’re trying to reproduce this error and so far have been unable to. Can you give some more details?

    Were you on the latest version of Atomic Blocks already when you upgraded to WordPress or did you also upgrade Atomic Blocks in the process?

    If you did upgrade Atomic Blocks at the same time, do you know which version you were on prior to upgrading?

    All my plugins are automatically update bij Jetpack. The only update I did myself was WordPress 5.0 to 5.1. For me the problem still occurs with a fresh made CTA-block on version 1.5.2 on WordPress 5.1. It shows fine on the website and I can “solve” the problem by converting it to a HTML-block.

    Hi,

    I freshly installed the atomic blocks theme and plugin (newest version) on a new WordPress 5.0 installation a few days ago. At that time everything worked just fine.

    The first and only update I made was to WordPress 5.1 and that’s where the problem began.
    I am also not using any other plugins on my site so far.

    Thanks for your support and the nevertheless great theme and plugin!

    Plugin Author John Parris

    (@mindctrl)

    Thanks for the info. WP 5.1 introduced a change that’s causing this. We’re working on it now and we’ll update you as soon as possible!

    Plugin Author atomicblocks

    (@atomicblocks)

    Hi there,

    The latest version of AB, 1.5.3, should fix this bug. Go ahead and update and check it out. Be sure to hard refresh in your browser to knock out any cached JS.

    works like a charm! Thanks for the quick response.

    Works great! Thanks for the fast support!!

    Plugin Author atomicblocks

    (@atomicblocks)

    @staartmees @paddy3001 Be sure to add a quick review! Helps us keep up the ratings and helps us get more resources for support and updates!

    Fixed now. Thank you for the fast response.

Viewing 14 replies - 1 through 14 (of 14 total)
  • The topic ‘Whitescreen an JS exception when editing site’ is closed to new replies.