SiteBuilder release notes

We released SiteBuilder 2.537 on Tuesday 21^st March 2023. In this version, we:

• Fixed a bug that caused Buttons components to display an error when editing a page in Firefox.
• Added the option to display News feeds as Tiles instead of a List. This option is available for both the News page template and the News feed component in the Components Editor.
• Added the option to create visually-editable blocks within Custom HTML components. Any content you put between <editable-block> tags in a Custom HTML component is editable from the main Components Editor screen, instead of requiring you to edit the HTML directly. Full details can be found in our updated guidance on how to use your own HTML and CSS.
• Removed additional space underneath blocks in the Components Editor. Layout blocks with the Flush to content above option selected will now correctly display with no gap.

We released SiteBuilder 2.536 on Wednesday 15^th March 2023. In this version, we:

• Changed the location of the Convert to Components Editor button on the Current page tab in SiteBuilder, to reduce the likelihood of users accidentally selecting it when trying to edit the centre content of a visual editor page. The button is now located farther down the Manage content section.
• Updated text when creating a Module page to inform users that the module code should include CATS, and clarify the required year format. Module pages use the full four-digit value for the starting year, for example 2022 for the 2022/23 academic year.
• Fixed a bug that caused a server error if a Module page was created with an invalid year.

We released SiteBuilder 2.535 on Wednesday 8^th March 2023. In this version, we:

• Implemented a new Item filter page template for the Components Editor (it's not available for the old visual editor). This can be used to create blocks of information - for example, staff profiles - which can then be filtered by users via assigned tags.
  Note: This page type is currently available as Beta functionality and is not shown by default among the available templates when creating a new page. See the Item filter help page for details.
• Fixed a bug that prevented users from adding a styled block inside an existing layout block.
• Fixed a bug that added an unnecessary line break when trying to add custom text styles to part of a sentence.
• Made Resource bookings pages clearer by adding borders around periods of unavailability and bookings made by other users.
• Changed the requirements for the Tabs/accordion component to allow a single entry. This was to enable users to add a single accordion item to a page.
• Upgraded to the latest version of FontAwesome 5, which improves the selection of icons available to web editors.

We released SiteBuilder 2.534 on Thursday 16th February 2023. In this version, we:

• Made a change to Custom HTML components so they no longer display the text 'HTML-DATA' when left empty. Custom HTML components without content will now appear blank, but retain their dotted line border in the editor to indicate their position and enable you to select them.

We released SiteBuilder 2.533 on Monday 13 February 2023. In this version, we:

• Fixed a bug that prevented filter tags working on News filter and Calendar filter page templates.
• Solved an issue where setting a period of unavailability with a long duration and frequent recurrence could cause performance issues on Bookings pages. With this update, trying to set a period of unavailability that could cause this kind of problem will produce an error message.
• Made the following fixes and improvements to the Components Editor:
  • Fixed a bug that meant Custom HTML components containing no visible content could not be selected in the editor.
  • Added an option to pause automatic accessibility checks while editing a page. This can be done by selecting the Pause live accessibility audits button, which is located next to the Re-check accessibility now button at the top of the Accessibility pane. While paused, the Components Editor will not automatically check for accessibility issues, which will improve editor performance while working on larger pages. Resuming audits or attempting to Publish the page will trigger an audit, highlighting any issues of concern.