This update introduces a new capability for form redirection within the Form Builder. As a CMS Admin, you can now include values entered into the current form as parameters in the redirection URL.

Previously, redirection URLs could only use session, path, query parameters, or constants. Now, you can use a "field" value from another field in the form using the token {f:FIELD_ID} (e.g., {f:25382}). This allows for more dynamic and flexible filtering of listing blocks or other customized redirections based on user input.

Deployment to Production: February 20, 2025.

This update implements dedicated error pages (400, 403, 404, 500) for LlamaSite for Salesforce (LLS) in HOC. These pages are now editable within the CMS, allowing for customized content for each error type.

Additionally, for pages using a "/p/" parameter where a parameter is missing, a new CMS page has been created. This page will display a default message: "Oops, it looks like the URL for the page you are trying to reach is missing one or more required parameters," providing clearer guidance to users.

Deployment to Production: February 20, 2025.

This update significantly enhances the multi-timezone compatibility within the HOC4 (HandsOn Connect 4) platform, especially for the Listing CMS. Previously, there were missing functionalities preventing full timezone support.

The following key improvements have been implemented:

• Timezone Abbreviations in Listing CMS: Timezone abbreviations are now properly integrated into the Listing CMS.
• New Database Fields for Custom Forms: Two new database fields, TimezoneForDate and TimezoneAffectedField, have been added to the FormFields level. These fields enable timezone functionality for associated date-time fields, particularly useful when editing occurrences.
• New Special Tokens for Listing CMS Block: New tokens have been introduced for both Data tables (ls:timezone({<date-time>}, {location-id-field})) and Custom Card Templates ({ls:timezone({<date-time>}, {{location-id-field}}), "<format-date>"}) within the CMS block. These tokens function when the multi-timezone feature is enabled.
• Enabling Multi-Timezone for Existing Sites: For sites created prior to this deployment that need to enable the multi-timezone feature, a streamlined process with specific changes has been developed and documented.

These updates ensure that the multi-timezone feature is fully compatible and functional across HOC4, providing accurate time display and management.

Deployment to Production: February 20, 2025.

This update resolves an issue where the Login Block settings were not accessible within the new Content Management System (CMS) layout. This prevented administrators from configuring and managing login functionalities.

The fix ensures that the Login Block settings are now fully available and editable in the new CMS, providing complete control over login configurations.

Deployment to Production: February 20, 2025.

This update resolves a bug in the Content Management System (CMS) where, in Content Pages, saved font size values were not correctly displaying in the visual editor. While the values were saved, they were not rendered accurately in the visual preview.

The cause was an incorrect validation for the stored font size value. A fix has been implemented to ensure that the correct font size values are now accurately displayed in the visual part of the CMS.

Deployment to Production: February 20, 2025.

This update addresses missing features in the new Content Management System (CMS) layout. Previously, the Form ID for each custom form was not displayed, and administrators lacked the ability to add a terminate and success page with the Advanced Registration System (ARS).

This fix adds the necessary logic to display the settings for both ARS Pages and the Form Builder, making these functionalities fully accessible within the new CMS layout.

Deployment to Production: February 20, 2025.

This update resolves an issue experienced during volunteer sign-up via the Advanced Registration System (ARS), specifically when a custom success page was configured. Previously, even if the custom success page was displayed, the volunteer's account might not be created, and related connections (like email flows) might not trigger.

The issue was caused by a bug in the logic that calculates and applies the correct success page settings. This fix ensures that the ARS successfully completes the sign-up process, correctly creating accounts and triggering associated actions when a custom success page is used.

Deployment to Production: February 20, 2025.

This update resolves an error message encountered by volunteer leaders when clicking on a volunteer's name in their portal. The issue prevented leaders from viewing volunteer details.

The problem was identified as a large query size being sent to Salesforce in the services. Adjustments have been applied to correct this issue.

Deployment to Production: February 20, 2025.

This update resolves an issue where CMS Administrators were unable to delete sliders within the new Content Management System (CMS) layout. Both the "delete" and "remove" buttons were non-functional.

The cause was a bug in the events related to these deletion links. The fix includes adjustments to the logic, allowing sliders to be successfully deleted and removed in the new CMS layout.

Deployment to Production: February 20, 2025.

This update resolves an issue with the Featured Opportunity Block where it was not correctly listing opportunities/occurrences by date order, defaulting instead to an incorrect order. This was particularly noticeable when attempting to reorder and save the block. Additionally, the block was not showing information from the next available occurrence.

The cause was identified as a change introduced in a previous release that affected the regular behavior. This previous change has been reverted to restore the correct functionality.

This ensures that the Featured Opportunity Block now accurately displays opportunities and occurrences in the correct date order and shows information for the next available occurrence.

Deployment to Production: February 20, 2025.

This update resolves a critical issue allowing individuals to sign up for activities, even though the Advanced Registration System (ARS) should have redirected them to a terminate page.

The problem was caused by incorrect validation in the conditional logic that executes when the "Signup" or "Express Interest" button is clicked. The fix ensures that the ARS now correctly applies the conditional logic as configured, preventing unapproved individuals from signing up for activities.

Deployment to Production: February 20, 2025.

This update resolves an issue where loading more results would cause filter sections to duplicate. This resulted in a cluttered and confusing display of filters.

The problem was caused by a client-side routine that was adding new filter sections each time the table reloaded, without checking if those sections already existed. The client-side logic has been refactored to include necessary validations, preventing the duplication of filter sections and ensuring a clean and functional display.

Deployment to Production: February 25, 2025.

This update resolves an issue where the color selected for an image in the image block was not being saved within the Content Management System (CMS).

This problem was related to LHH-20793, and the fix ensures that the selected color now saves correctly, providing consistent styling for images.

Deployment to Production: February 25, 2025.

This update resolves an issue in the new Content Management System (CMS) layout where the button to add a new "Featured Opportunity Block" was missing. This prevented administrators from creating and managing these important content blocks.

The problem was due to missing markup and logic for creating the block in the new CMS. This has been corrected, and the button and its associated functionality are now fully available.

Deployment to Production: February 25, 2025.

This update resolves a formatting issue in the new Content Management System (CMS) layout that prevented users from accessing the quick-access "edit form" button from a modal window. The "X" (close) icon was overlapping and obstructing the edit button.

The problem was a styling conflict. The fix involves adjusting the styles to correctly position the edit icon below the close icon, making it fully accessible for administrators.

Deployment to Production: February 25, 2025.

This update resolves an issue where opportunities marked as "To Be Scheduled" were not appearing in the Featured Opportunity Block. This prevented these opportunities from being prominently displayed on relevant pages.

The fix addresses a bug in the logic that renders records for the Featured Opportunity Block, ensuring that opportunities of the "To Be Scheduled" type are now correctly included and displayed.

Deployment to Production: February 25, 2025.

This update resolves an issue in the new Content Management System (CMS) layout where the image block was not updating after an image upload and save, despite a success message appearing. Additionally, the "Browse" and "Delete" links within the new CMS Layout for image blocks were not functional.

The problem was due to missing logic for the browse and delete functionalities, as well as a bug in the image storage process. This fix includes the necessary adjustments to resolve these issues, ensuring that image blocks update correctly and all associated links function as intended.

Deployment to Production: February 25, 2025.

This update addresses an issue where the keyword search field would only return exact matches for terms, particularly affecting variations of acronyms (e.g., "LGBT," "LGBTQ," "LGBTQIA+"). Previously, searching for "LGBT" might not return results containing "LGBTQ" or "LGBTQIA+".

The SOLR search engine now supports searching for related terms by adding an asterisk (*) to the end of the word (e.g., searching "LGBT*"). A helper element has also been added to the search page to indicate this option. This ensures that searching for a root acronym or term will yield results containing its variations, providing a more comprehensive and intuitive search experience.

Deployment to Production: February 28, 2025.

This update resolves a critical issue preventing the submission of custom forms, which was reported by multiple clients. The forms would not indicate any errors but simply fail to submit.

The cause was identified as a bug where "required" validation was still being applied to calculated fields, even when those fields were located in hidden sections of the form. The logic for calculated fields has been updated to skip validation for fields that are in hidden sections, ensuring forms can now be successfully submitted.

Deployment to Production: February 28, 2025.