• Resolved PaulProv

    (@paulprov)


    Hey guys,

    Thanks for putting back the Container block. However, once I converted the block to Column Manager, the class of the container was gone. My page sections gets messed up coz the col manager has different classes.

    Please dont remove the container block in the future versions coz I have already created several Reusable blocks using that. I also used it as nested container like Container block inside a parent Container block which I have styled already in css.

    Kindly retain the block in future versions so we dont have to restyle a lot of css in lots of pages.

    Thanks!

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

    We’ve created the container block to work with the Gutenberg column manager.
    We were thinking that the default Gutenberg column manager would be suitable for most of the usages but we found out that is was not usable at all.

    We have made the choice to create our own column manager. At this time the container block is not necessary anymore for new content.
    We’ll keep it as long as it works with the current Gutenberg version, but we can’t maintain indefinitively a block which is not anymore available for the users.

    I understand it could be frustrating, but in order to improve the overall plugin, we have to make choices like this one.
    You can now rely on this new block, it will always be supported.

    In any case soon or later it would be better to convert all your blocks to avoid any problem.

    You can convert your reusable block to the new column manager, please have a look here: https://drive.google.com/file/d/1wdmE9lWVddA74yjP4XG8r3rHhC5dnC5Z/view?usp=sharing
    For reusable blocks already inserted in content you can convert them to regular block and then convert it to column manager block.
    Of course you may need to do a search and replace in your css stylesheet to change the old container classes to the new column block one.

    Best regards

    Thread Starter PaulProv

    (@paulprov)

    Hi Devs,

    I know the Container may sound not useful for columns. But I have used like a simple div container for simple things. Like when I just want a centered title on a section then below it, I want to put image blocks inside a Container. Then I make those images inside the container as slider. This way it is easier to control in js and style in css without having to override css for columns.

    The default Gutenberg of WP doesnt have a Container element for simply adding new sections in a page without the need for a row and columns. Please believe me your Container element is very useful that what is seems.

    I’m a dev and I prefer more control on elements in css but I also want to retain the visual editing capabilities of gutenberg.
    Without the container, if I want to add a custom section as a div or section element, I will need to use Custom html block. But once I use it, I wont be able to drag and drop image elements inside it.

    I hope you understand how awesome your Container element is and I’ve uninstalled other Gutenberg plugins because they dont offer adding Container block that can be drag and dropped.

    So many times, especially custom sections, there is not a need to add a row and columns. We just need to be able to add a container element and add other Gutenberg elements in it.

    I really hope you consider my request.

    Thanks and more power to your team!

    Hi,

    Thanks for the clarification, I understand the request.
    Can you tell me why you find it different from a single column block (ie a row)? Because you also have some div and containers with style to apply on, see:

    https://drive.google.com/file/d/1zs2cj3Ut4Fb9GNcGrCPmQPTSWKOxAe3T/view?usp=drivesdk

    Let me know, cheers,

    Thread Starter PaulProv

    (@paulprov)

    Hi,

    Thanks for understanding my request. A single column block will need a wrapper like a row or container which is an additional html element that isnt really necessary for simple custom sections.
    Plus, a single column block, for sure, has pre-styled css already to be stable whereas a simple container block can be a simple div or section block with no complicated styles in css. That makes it easy to override for devs.

    Thanks

    OK I got it, you can do it but you’ll get a cleaner code with the section.

    We may re-introduce it in the upcoming version but not activated in the profile by default, you will need to re-enable it in the Advanced Gutenberg profile.

    Cheers,

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

The topic ‘Container block class gone after conversion’ is closed to new replies.