Release 6.0 Summary

May 5, 2022 

by

 

Notice Banners

Notice post types now have more granular controls, so that a banner/notice can be overridden on the page level. Detailed instructions can be found on the Notice Post documentation page.

  •  Ability to show different notices on different pages See screenshot.
  •  Ability to set ‘no banner/notice’ on certain pages
  •  Ability to show a different notice on desktop & mobile
  • Ability to set an unpublished date for banners, so that we can select a future date for the notice/banner to unpublish; adds a new toggle to enable/disable the unpublish date (disabled by default). See screenshot.

Global Settings

  • New option to Global Settings (under Settings > Taxi & Settings > Analytics) to remove Optimizely script from being loaded on supported post types (Pages, Posts, PLPs). See screenshot.
  • New options to Global Settings (under Settings > Taxi & Settings > Taxi) to remove Taxi script from being loaded on supported post types (Pages, Posts, PLPs). See screenshot.

Other

  • On the All Pages admin page, a column has been added to show which Form ID(s) are in use on each page. See Screenshot.
  • Adds new options to enable the Taxi and Optimizely scripts on a page/post level. (Page > Script Options). See screenshot.
    Note: future enhancement will be to enable taxi/optimizely to be disabled on a page level. Current settings are meant to be used if Optimizely/Taxi is disabled in the global settings, to allow certain pages to have Optimizely/Taxi enabled.
  • Removal of unused fonts (Inconsolata and Open Sans) so that all font references are via Vibram.

Workarounds and Updating Blocks

As discussed on the Web Production team call, there are some temporary workarounds that may be required when working with legacy blocks that need to be updated to the v2 “refactored” blocks. More information can be found in the Workarounds sheet. Tab 2 of this document includes a list of all blocks that can be updated to the v2 version.

One note on Forms: Legacy forms can stay as they are; there is no need to update these. There is also no ‘update’ option, but you may notice for any new forms created, the new Form block (rather than Form (Legacy) will be used. The only form type that currently should only use the Legacy form block is Airtrain. The engineering team is working an update to Airtrain to allow forms on umbrella sites, and will be rolling this out to each program. Until a program has been giving the green light, please continue to use the Form (Legacy) for Airtrain forms.

What does “Block Refactor” work mean:

  • Parallel WordPress core block code as standard 
  • Reduce CSS and JavaScript where possible 
  • Keep the editor experience consistent, use shared components if they exist e.g. spacing selectors 
  • Follow standard deprecation structure / follow core blocks
  • Convert to PHP render