Release notes for web applications

We released Tabula 2022.8.1 on Wednesday 27^th July 2022. In this version we updated the tooltip that appears when the button to self-certify on a student's behalf is disabled, to include situations where no extension manager has been allocated.

We released Tabula 2022.7.4 on Wednesday 27^th July 2022. In this version we:

• Fixed an issue where positioning the cursor near the edge of a point in a Marks Management scaling graph displayed an incomplete tooltip. We also fixed an issue where tooltips were cut off when browser windows were resized.
• Fixed an issue where pass/fail modules were causing issues with Suggested Results calculations in exam grids.
• Fixed a bug where mark/year weighting information was incorrectly displayed on module pages for students who have changed from 3- to 4-year courses.
• Fixed an issue that prevented resit-without-residence (RWR) students from deferring resits due to mitigating circumstances.

We released Tabula 2022.7.3 on Wednesday 21^st July 2022. In this version we added details of affected assessment components beneath the board recommendation in the Mitigating Circumstances column of exam grids.

We released SiteBuilder 2.516 on Wednesday 7^th September 2022. In this version we made the following bug fixes and improvements:

• We fixed a bug so that floated images now display as expected both in the Components Editor and on your published page.
• We fixed a bug which prevented converting pages that use the right hand content from another page. Please note that after conversion, if the content on the source page changes, the page you are on now will not automatically update. To achieve the same thing in the Components Editor:
  • Create a Components Editor page containing just the content from the right-hand side of the source page
  • Edit the page you are on now and add a Content feed from another page component (via the left-hand menu), setting its source page to the page you created above
• We fixed a bug which prevented users from checking for broken links on a set of pages.
• When a contents list displays multiple pages of results, it is now possible to sort the results. This sort order is persisted when browsing to the next/previous page. Previously, it was only possible to sort the results when displayed on a single page.
• When you use the Copy page contents feature on a page that's based on a page template, such as Glossary, News or Calendar, the target page is now converted to the corresponding page template and all your entries, such as glossary definitions, news items and events, are copied across. Previously, only the surrounding content of such pages was copied. Note that for pages based on templates which receive user data, such as Form or Bookings, this user data is not copied.
• We continued work which will enable complex pages such as homepage layouts to be converted to the Components Editor.

We released SiteBuilder 2.515 on Thursday 4^th August 2022. In this version we made the following bug fixes and improvements:

• We improved the validation message displayed to make it clearer when a researcher profile can't be fetched from Ideate. You can add a researcher profile component to your page by selecting Add special features from the left-hand menu and selecting Researcher profile from the sub-menu.
• We improved how hero blocks and their text are displayed on smaller screens, such as mobile devices. You can add a hero block to your page by selecting Add layout blocks from the left-hand menu and selecting the Hero block option from the sub-menu.
• We fixed a bug which caused glossary terms to inherit the text colour of the container. You can add a glossary term to your page by selecting Add links and anchors from the left-hand menu and selecting Glossary term link from the sub-menu. You'll then be able to select the appropriate Glossary page and the specific Term you'd like to add to your page.
• We fixed a bug which prevented users from uploading files which contained certain special characters in the filename.
• We fixed a bug so that the site content report only displays accessibility audit data for HTML pages. We introduced these columns to the site content report in 2.514.