Stopped working with Gutenberg v17.5.0

  • Resolved George

    (@subscriptiongroup)


    10 months, 2 weeks ago

    We’re using the Gutenberg plugin (rather than the stock version) and we’ve just upgraded to the latest version 17.5.0, but Block Visibility seems to have stopped working. Reverting Gutenberg to v17.4.1 resolves the problem.

    Simple elements like paragraphs work fine, but more complicated logic like images inside a group, have stopped working.

    Steps to reproduce

    1. Create a new page.
    2. Add a group block.
    3. Add an image block inside the group and leave its visibility unchanged.
    4. Add an image block inside the group and change its visibility to hide on desktop, and hiden on tablet.

    Expected Results
    The second image should show on mobile.

    Actual Result
    The second image never shows up.

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Nick Diego

    (@ndiego)

    Thanks for reporting this @subscriptiongroup. I am able to replicate and will report in the Gutenberg repo.

    Best,
    Nick

    Thread Starter George

    (@subscriptiongroup)

    Thanks @ndiego

    I’m not sure why you’d think this is a GB issue rather than something that needs changing on your plugin?

    Here’s another report on their support page saying Yoast is also broken with the latest version, but that’s probably for Yoast to resolve?

    Plugin Author Nick Diego

    (@ndiego)

    I’m not sure why you’d think this is a GB issue rather than something that needs changing on your plugin?

    There looks to have been a change specifically to the Image block that is causing this issue. The method the plugin uses to apply the classes for the Screen Size control has worked for the last few years, so this is a breaking change for backward compatibility.

    Before I make any changes in the plugin itself, I need some additional direction from the Core team about whether this was an inadvertent break that can be fixed, or if this is going to be the status quo going forward.

    Here is the logged issue for reference.

    Plugin Author Nick Diego

    (@ndiego)

    After more testing with the latest changes in Gutenberg, which will be released in 17.6, the bug is resolved. The issue has more details.

    I am going to keep this support ticket open until Gutenberg 17.6 releases and we have confirmed that the bug is indeed resolved.

    Thread Starter George

    (@subscriptiongroup)

    thanks for the prompt reply!

    Plugin Author Nick Diego

    (@ndiego)

    Hi?@subscriptiongroup,

    I just retested this bug in Gutenberg 17.6, and the issue seems to have indeed been resolved. Once upgrading to 17.6, if you continue to experience any issues, please let me know.

    Best,
    Nick

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Stopped working with Gutenberg v17.5.0’ is closed to new replies.