Why do Container blocks require Rows and Columns?

  • Resolved conducivedata

    (@conducivedata)


    1 year, 4 months ago

    As the subject says, why do Container blocks require Row and Column blocks? I can work around that by creating a Div block and adding the .container class, but I don’t understand why Container blocks force at least one row and one column. When writing code by hand, I use .container divs without rows all the time.

    I appreciate your efforts and the regular updates on this plugin. Keep up the good work!

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author all_bootstrap_blocks

    (@areoimiles)

    1 year, 4 months ago

    Hi @conducivedata

    I’ve just released an update which removes this restriction so you can now add any block inside the container block. When you add a container block it will still automatically add a row and column as this is the most used configuration for this block, however, now you can remove the row and column and use the container freely.

    Hopefully this helps with your use case. Thanks for reaching out and if you need anything else, please don’t hesitate to get back in touch.

    Miles

    Thread Starter conducivedata

    (@conducivedata)

    1 year, 4 months ago

    Oh wow, thank you, @areoimiles! I was definitely not expecting such a quick and helpful response! I just did some testing, and it mostly works. Works enough, which is great.

    The only issue I see so far is that it’s a real challenge to drop blocks into an empty Container without using the blocks List View. It’s much easier once a block is inside the Container, however it still won’t let me drop one in there when dropping in a new block.

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

The topic ‘Why do Container blocks require Rows and Columns?’ is closed to new replies.