Support » Plugin: Stackable - Gutenberg Blocks » After update every button block broken

  • Resolved Torsten Landsiedel

    (@zodiac1978)


    After the latest update (or maybe the one before) every button block is broken in my website. I just get “This block contains unexpected or invalid content.” and there is no way to fix this. I need to rebuild the button. Any idea why this happens and how to prevent this?

    All the best,
    Torsten

Viewing 10 replies - 1 through 10 (of 10 total)
  • Plugin Contributor gambitph

    (@gambitph)

    Hello Torsten,

    We’re sorry to hear about that. Can you tell us by any chance what version number you’re using prior to updating? Normally the icon should be fine, but it may be also possible that either the last version you’re using was a huge leap to the latest version or there might be a particular setup that’s causing the issue.

    If that may be the case, we’ll need to know more about your setup so we can replicate it. Thanks! πŸ™‚

    Can you tell us by any chance what version number you’re using prior to updating?

    I think I updated from 1.11 to 1.12.1, so no huge step here …

    This wasn’t any fancy stuff. It is just a button with a link. I just customized the color. It doesn’t matter what I click now. At the end I get plain HTML and need to rebuild the block. πŸ™

    Any ideas how to fix this?

    All the best,
    Torsten

    Plugin Contributor gambitph

    (@gambitph)

    We tried to replicate the issue by creating different colored buttons using 1.11 and updated it to 1.12, we haven’t encountered the issue in our end.

    Can you provide us with your HTML/raw version from your page? We’ll try to compare and paste it in our sandbox and see if there’s something in the code or if there might be something like another plugin involved with the problem.

    You can paste your HTML and send us a link here: http://pastebin.com

    I have several buttons and cards. Every button shows the problem (no matter if in column or not). But it is only the first card that has the problem on one page.

    I’ve summarized all the button/card blocks HTML in one pastebin:
    https://pastebin.com/k05SiQkT

    I’ve spotted one problem with unmasked spaces in a URL and a doubled @ in the href/mailto, but as the other buttons have the same problem this shouldn’t be the culprit here …

    Hopefully you can see more than me …

    All the best,
    Torsten

    Plugin Contributor gambitph

    (@gambitph)

    Sorry for the late reply. We just found the issue and it’s related to the buttons. We have our fix on the issue and we’ll update Stackable in a day or two! πŸ™‚

    Hi @gambitph,

    after the update to 1.13.0 its even worse. Now I can’t save any page withj a button in it, because this error from the console:

    Block validation: Block validation failed for ugb/button (
    Object { name: “ugb/button”, title: “Button”, icon: {…}, description: “Add a customizable button.”, category: “stackable”, keywords: (2) […], attributes: {…}, supports: {…}, sDemoURL: “https://wpstackable.com/button-block/?utm_source=welcome&utm_medium=settings&utm_campaign=view_demo&utm_content=demolink”, edit: t()
    , … }
    ).

    Expected:
    <div class=”wp-block-ugb-button ugb-button-wrapper ugb-button–align-center”><div><span class=”ugb-button–inner”>Mehr Infos …</span></div></div>

    Actual:
    <div class=”wp-block-ugb-button ugb-button-wrapper ugb-button–align-center”><div><span class=”ugb-button–inner” style=”color:#ffffff”>Mehr Infos …</span></div></div>

    Deleting and re-adding the button does not work either.

    πŸ™

    Any chance for a quick fix?

    All the best,
    Torsten

    Plugin Author Benjamin Intal

    (@bfintal)

    Hi,

    I know we fixed this already. I’ll investigate again πŸ™‚

    Plugin Author Benjamin Intal

    (@bfintal)

    Hey Torsten,

    Would it be possible to check things out from your actual site? I’ve checked the pastebin you sent and that one works fine already. So there must be an edge case not handled here.

    If you can send over your site login details to our email support@wpstackable.com, I can check what’s happening.

    So there must be an edge case not handled here.

    Maybe conflict with another plugin? Would it help to send you the other active plugins?

    If you can send over your site login details to our email support@wpstackable.com, I can check what’s happening.

    I don’t think thats possible for my client site. And I think asking for this is forbidden in these forums too:

    Forum members, including plugin and theme authors, should never ask for admin or FTP access to a server, MySQL, or WordPress installation.

    https://make.wordpress.org/support/handbook/contributing-to-the-wordpress-forums/privacy-issues/

    All the best,
    Torsten

    I’ve found the “bug”. It was the mod_security implementation of the hoster which was causing this. Every (auto-)save request was replied with an 503 service unavailble. After disabling mod_security I was able to save again.

    Sorry for the trouble!

    All the best,
    Torsten

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