Problem/Motivation
After applying the 1.8 release of CivicTheme and running updates, the configuration was not automatically updated for:
1. The enabling of the 3-column layout and and disabling of the single column layouts in the allowed layouts for the Page content type.
2. Switch to 3-column layout for Page content type
3. Update to all blocks residing in the `sidebar` region to use `sidebar_top_left` region.
Steps to reproduce
1. Install CT 1.8 on existing CT site.
2. Run updates
3. Observe that the pages look more narrow.
4. Observe that side navigation block has disappeared.
5. Go to view mode of the Page content type and observe that "3 column" layout is not enabled
6. Go to view mode of the Page content type and observe that "3 column" layout is not used
Proposed resolution
Create 2 update hooks to address the issues above. Note that for the layout switch, the update hook should update to the new layout ONLY if the original layout was not changed (the block in the active config are the same as in the CT 1.7 config); if they have changed - skip the update and notify the user.
Manual workaround
1. Install CT 1.8
2. Run updates
3. Export configuration
4. Assess the config yaml files and update the side navigation (and any other blocks) to use `sidebar_top_left` region. Also, revert the status of this block to be `true`.
5. Copy `civictheme/config/install/core.entity_view_display.node.civictheme_page.default.yml` to your active configuration
6. Run configuration import
7. Run configuration export again
8. Observe that the site looks correct now
| Comment | File | Size | Author |
|---|
Comments
Comment #2
joshua1234511Testing Notes
- Switched to tag 1.7.1
- Build Drupal site (New Build)
- Switch to branch `feature/3458260-missing-update-hooks`.
- Update/ Build child theme code.
- Clear Cache
- Review the site and validate that the issues exist.
- Run update DB code.
- Review the site and validate that the issues have been fixed.
Before


After


Test Result: Reviewed the site and validated that the issues have been fixed.
Comment #4
alex.skrypnykImplemented and released in 1.8.1
Comment #5
alex.skrypnyk