This ticket involved a review of previous versions of CMS Blocks (HTML editor, button, and RSS blocks) within the new Layout CMS. This ensures that these blocks function correctly and are fully compatible with the updated CMS, providing a smoother experience for content management.

Deployment to Production: January 23, 2025.

This update changes the default layout for the Content Management System (CMS) to the new layout. This ensures all users will now experience the updated and improved CMS interface by default.

Deployment to Production: January 28, 2025.

This update addresses an accessibility issue where strikethroughs on dates within the date picker component were not visible in Windows High Contrast mode. The problem was due to the visual design using semantic form without a text alternative for visual impairment.

To resolve this, additional styles have been added to the component, ensuring that the date picker now meets accessibility standards.

Deployment to Production: January 23, 2025.

This update resolves an issue where the "Partner Portal Dashboard" menu item would incorrectly rename itself to "partner portaldashboard" every time the page was edited and saved in the CMS. This was a validation issue that caused the title to revert.

With this fix, the menu item will now retain its correct title, "Partner Portal Dashboard," consistently.

Deployment to Production: January 23, 2025.

This update addresses an issue in custom forms where it was not possible to assign different labels and values for multi-select picklist fields. Previously, the system did not allow for this distinction, limiting flexibility in form design.

With this fix, you can now define and assign different values for labels and options in multi-select fields, similar to how single-select fields function. This provides greater control and customization for your customer forms.

Deployment to Production: January 23, 2025.

This update resolves an issue with the saved search page where the "View/Edit" button was unnecessarily displayed and the text "searchresultblock" appeared after each search.

The "View/Edit" button and the extraneous "searchresultblock" text have been removed, providing a cleaner and more user-friendly experience for saved searches. This issue was caused by a bug in how saved searches were stored in the database, which has now been fixed.

Deployment to Production: January 23, 2025.

This update resolves an issue where configuring multimedia settings for a region would incorrectly generate an <img> tag instead of applying the image as a background URL via CSS. This caused problems with image resizing and responsiveness.

The fix ensures that images in regions with multimedia settings are now correctly displayed as background images using CSS, improving how they are rendered and resized.

Deployment to Production: January 23, 2025.

This update resolves an issue in HOC4 where tables were displaying hidden columns and had misaligned columns, particularly affecting listing CMS blocks. This was due to a compatibility issue with a recent improvement in how data tables were populated.

The method for building table headers has been modified to ensure compatibility with existing tables, leading to correctly displayed and aligned columns.

Deployment to Production: January 23, 2025.

This update resolves an issue where team member records created through opportunity sign-ups were incorrectly assigned as 'Food Programs Staff' instead of 'Volunteers,' and the team captain's account type was incorrectly set to 'Individual.'

The following fixes have been implemented:

• Fix for Incorrect Contact RecordType Assignment: Updates were made to the LLSHOC Automations Package v1.13 to ensure the correct Contact.RecordType is set according to the FLEX configuration.
• Fix for Contact Account Being Incorrectly Set to Individual: Adjustments were applied in the HOC-Search-Service Project to address the issue of Contact.Account being improperly assigned as "Individual."

These changes ensure that team member records and account types are accurately categorized, providing correct data for reporting and management.

Deployment to Production: January 28, 2025.

This update resolves an issue where the "Next" button was not appearing on mobile devices for certain forms. This prevented users from progressing after completing a quiz or form.

The cause was a bug in the logic that determined whether the "Next" button should be displayed or hidden when the page loaded on mobile. This has been fixed by adding the necessary validation to ensure the button's visibility is correctly controlled based on its display logic.

Deployment to Production: January 28, 2025.

This update resolves an issue where users encountered an error message when attempting to register with a Google account, specifically when the site had an ARS (Advanced Registration System) for registration but none of the branch logic rules were applied. This prevented Google sign-ups from completing.

The logic responsible for handling the "next" event during registration has been updated to correctly submit to the final page in this specific use case, allowing for successful Google sign-ups.

Deployment to Production: January 28, 2025.

This update resolves an issue that caused errors when updating blocks in the new Content Management System (CMS). Previously, an ArgumentNullException (value cannot be null) would occur, preventing successful updates of certain blocks, particularly menu and image slider blocks.

This fix includes additional validations and changes in the logic to prevent issues arising from corrupted lists within these blocks. This ensures a more stable and reliable experience when updating content in the new CMS.

Deployment to Production: February 3, 2025.

This update resolves an issue where the Listing Block's path was not correctly retrieving values based on the ID in the URL parameter, especially when accessed via a partner portal link. This caused incorrect information to be displayed in the path graphic.

The server-side logic has been updated to correctly handle the URL values that generate the listing in the CMS, ensuring accurate data representation.

Deployment to Production: February 3, 2025.

This update resolves an issue where certain items were not appearing in the main navigation menu of websites, even though they were enabled in the CMS. This specifically affected menu items with empty URLs, as a previous validation incorrectly prevented their display.

The validation logic for menu item URLs has been adjusted to correctly allow menu items with empty URLs to display, ensuring all enabled navigation items are visible on the website.

Deployment to Production: February 3, 2025.