• I’m using the Spacious theme with the WordPress Block Editor and have run into an issue with the Columns block border setting.

    I have an outer Columns block containing three columns. In the Block Editor, under Styles → Border & Shadow, I have set a 2px border.

    The border displays correctly inside the Block Editor, but when I view the published page on the front end using Spacious, the border does not appear.

    To determine whether this was a Gutenberg issue or theme-specific issue, I tested the same page/block setup with several other themes.

    The border displays correctly on the front end with:

    • Twenty Twenty-Five
    • Hestia
    • Kadence
    • Ashe
    • Sydney

    The border does not display with:

    • Spacious
    • OceanWP

    So the border setting appears to be saved correctly by the Block Editor, but something about the front-end styling in Spacious seems to prevent it from being displayed.

    I’m specifically trying to use the native Gutenberg Border & Shadow control, rather than adding a custom CSS border, because I am teaching beginners how to use the Block Editor and want the front-end result to match what they create using the editor controls.

    Is this a known issue with Spacious, or is there a theme setting or block-support setting that needs to be enabled for Gutenberg’s native Columns border to display on the front end?

    I’d be happy to provide screenshots or any additional information needed.

    Thank you!

    The page I need help with: [log in to see the link]

Viewing 2 replies - 1 through 2 (of 2 total)
  • Hi christinahills,

    Thank you for the extremely detailed report and for testing this across multiple themes. That really helps us pinpoint the issue quickly.

    We have replicated this on our end as well. You are right, the Columns block border saves correctly through the native Gutenberg Border & Shadow control, but Spacious’s front end styling is currently preventing it from displaying, even though it shows correctly in the editor.

    The fix for this will be included in our upcoming theme update. We will follow up here once it is released.

    Thank you again for the thorough testing and for helping us catch this.

    Best regards

    Thread Starter christinahills

    (@christinahills)

    thank you so much for being responsive!
    I look forward to the update 🙂

Viewing 2 replies - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.