Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
When I select 'page - Stored in database' and process it, then disable one or more regions and save the layout with Layout file store mode set to 'Store in database, variable table' the disabled regions are not disabled.
If I add regions which default to disabled, it correctly saves them into the layout, but it is then not possible to disable them again.
I have ensured that the disabled regions are empty (In fact as a test I enabled a region and then tried to disable it having never added anything).
Comments
Comment #1
duckzland CreditAttribution: duckzland commentedcould you let me know what is the layout file name that you save to database? eg. (page.layout or page--blog.layout) ?
because for example you save page--blog.layout and disable x region to database, this means that only all blog type page will have x region disabled.
The other pages will fallback to page.layout and if in page.layout x region still available then theme will print it when you view other page aside from blog type.
Comment #2
ITMonkey CreditAttribution: ITMonkey commentedThis is for page.layout - I have not customised any specific files, everything is default apart from page.layout stored in database.
Comment #3
duckzland CreditAttribution: duckzland commentedok I'll look into it.
so basically
1. the layout is page.layout
2. you've stored the layout to the database
3. reopen the stored layout in the database
4. change things around and resave again
5. the latest changes don't get stored
is that the workflow? so I can simulate it.
Comment #4
ITMonkey CreditAttribution: ITMonkey commentedThe workflow is correct, except that I CAN move things around and enable regions, I simply can't disable them. It's almost as if disabled regions don't have a row so previously enabled regions, when disabled, are missed entirely during the save process and therefore, when re-processed, the previous row in the database is used.
Comment #5
duckzland CreditAttribution: duckzland commentedOk thanks for the information.
I'll sort this asap in the weekends.
Comment #6
duckzland CreditAttribution: duckzland commentedFixed in beta16. Please download the latest version.