Cannot edit custom theme grid columns amount
Permalink
Hello,
I'm learning my way around theming for 5.7. I've packaged a really basic theme which essentially has no real design to it. I'm not a big fan of the amount of excess classes bloat that prepackaged grid systems have so I css'ed up my own very simple grid that I've been using for a while now.
I was thrilled to see that I could include my simple grid in a packaged theme for use in layouts and went about doing so. It works as expected, I can create new layouts, choose how many columns and it works fantastic. However when I go to edit a layout I've placed, I can't change the amount of columns. Is this normal behavior?
See my screen shot attached, you will see the up and down arrows are missing on the columns field, I can't click in there or anything to type a number in.
Thanks
I'm learning my way around theming for 5.7. I've packaged a really basic theme which essentially has no real design to it. I'm not a big fan of the amount of excess classes bloat that prepackaged grid systems have so I css'ed up my own very simple grid that I've been using for a while now.
I was thrilled to see that I could include my simple grid in a packaged theme for use in layouts and went about doing so. It works as expected, I can create new layouts, choose how many columns and it works fantastic. However when I go to edit a layout I've placed, I can't change the amount of columns. Is this normal behavior?
See my screen shot attached, you will see the up and down arrows are missing on the columns field, I can't click in there or anything to type a number in.
Thanks
Thanks for confirming. I guess that is the expected behavior. It's fine really, I'm sure it's because reducing columns could cause someone to lose their blocks in those removed columns or some other reason. It just means in training we will have to be sure to tell clients to create a new layout, move their blocks to the new layout, then delete the old layout.
It was possible in legacy C5 but it had other problems of its own...
I confirm it's the same with any grid. I wonder why. It doesn't look like a bug though, more like a feature but it's a bit of a pain