Theme 1.29 + SDK 1.14: Breaking Changes (Spring '22 Release)

Product/Library Releases & New Features Spring '22 Release
,
1

This version includes breaking changes - all upgrades to Theme 1.29 or later must follow the upgrade implication instructions below. The breaking changes have been consolidated into this post from the two breaking changes:

Upgrade Implications

Every vertical pages.html.hbs file in your experience must be refreshed if you upgrade to theme 1.29 or later. You can do this with one of the following approaches:

  1. Replace all the content in each vertical pages.html.hbs file with the content from the theme file (find this at themes/answers-hitchhiker-theme/templates/[page-template]/page.html.hbs). Then comment in any previously commented in filters, sorting, etc. that you would like to use. (Recommended)
  2. Recreate each vertical page using the Jambo Command “Add Vertical”.
  3. Update the page layout manually in each vertical pages.html.hbs file. Since this change affects a major portion of the files, only use this approach if you know what you are doing.

[page-template] refers to the page template used by each vertical. This would be vertical-standard, vertical-grid, vertical-full-page-map, or vertical-map. Note the filter and footer collision fix does not apply to either map page template.

Option #1 (replacing content with content from the theme) is the recommended approach as it is less time consuming than option #2 and less error prone than option #3. However, if you have a highly customized vertical, you may want to make the updates manually with option #3.

To make these updates manually, follow the instructions below:

  • First, update the page layout for Fix Filter and Footer Collision:

    1. Find the changes outlined here by template (vertical-standard, vertical-grid).

    2. For each page in your experience, find the changes in the file corresponding to that page’s template. Changes include moving a div up and adding new div containers. Red highlights show where code was moved from (deleted) and green highlights show where code was moved to (added) or added net-new.

    3. Make the corresponding change for each page in your experience.

  • Then, move the markup for Additional WCAG Update: Collapsible Filters Tab Order:

    1. Find the changes outlined here by template (vertical-standard, vertical-grid, vertical-full-page-map, and vertical-map).

    2. For each page in your experience, find the changes in the file corresponding to that page’s template. The changes in each file should only include moving the viewresultsbutton markup. The red highlight shows where the line was moved from (deleted) and the green highlight shows where the line was moved to (added). For example, the screenshot below shows that in the vertical-standard template, the viewresultsbutton markup line was moved from line 47 to line 54.

    3. Make the corresponding change for each page in your experience.

985×444 63.9 KB