HOC4 Release Notes 1.19.0

LLH4v1.19.0 (Released: 02/19/2026)

Overview

This HOC4 release resolves issues with password set emails, international phone number validation, opportunity coordinator fields, registration errors, and waitlist clarity during multi-shift signups. It also introduces a redesigned Menu Block layout, custom font support, and Skills menu item validation in the package manager.

🐞 Bug Fixes

LHH-22847 – Email not sending to set password

• What was the issue?

• When a volunteer's LlamaSite Profile was set for the first time, the system was supposed to send a "Welcome" email directing them to set their password. This email was not being sent due to a bug in the email template selection logic.

• What was solved?

• We fixed the template selection utility so it reliably retrieves the correct email body. The system now follows a clear priority: Lightning Email template first, then "HOC4"-prefixed, then "HOC"-prefixed, then any active match—ensuring the proper placeholders are used.

Result: New volunteers now receive their password setup email as expected when their profile is first created.

LHH-22846 – International Phone Numbers Error in Form

• What was the issue?

• When editing international phone numbers on forms, the system displayed a validation error, preventing partners from saving their changes.

• What was solved?

• We corrected the phone field validation so that international formats are accepted and the field clears properly when needed.

Result: Partners can now edit and save international phone numbers without encountering errors.

LHH-22830 – Volunteer Opportunity – Opportunity Coordinator Issue

• What was the issue?

• When partners edited a Volunteer Opportunity, the Opportunity Coordinator field appeared blank instead of showing the value pulled from the ORT (Organization Relationship Table). This was caused by an execution order issue with the Ajax calls that load the field's data.

• What was solved?

• We adjusted the sequence and execution control of the Ajax calls so the Opportunity Coordinator value is assigned only after the data has fully loaded.

Result: The Opportunity Coordinator field now correctly displays the expected value when editing a Volunteer Opportunity.

LHH-22817 – Cannot Register on ALP

• What was the issue?

• Users were encountering an error when trying to register through an Automatic Landing Page (ALP), preventing them from completing registration.

• What was solved?

• We identified and resolved the issue affecting the ALP registration flow.

Result: Users can now register through ALPs without encountering errors.

LHH-22782 – Waitlist receiving confirmation emails

• What was the issue?

• When volunteers signed up for multiple shifts at once and some of those shifts had waitlists, the system showed a generic "Success!" message for all shifts—including waitlisted ones. This caused confusion, as volunteers believed they were confirmed for all shifts.

• What was solved?

• We updated the multi-signup service to return detailed status information for each connection (Confirmed vs. Waitlisted). The success confirmation page now shows two distinct sections—one for confirmed shifts and one for waitlisted shifts. Additionally, a clarification message is shown before submission indicating how many shifts are for signup and how many are for the waitlist.

Result: Volunteers now clearly see which shifts they are confirmed for and which ones they are waitlisted for, eliminating confusion during multi-shift signups.

🆕 New Features / Enhancements

LHH-22837 – New Block Layout –  Menu Block

• What was the issue?

• The Menu Block configuration screen needed a redesign to prioritize the most frequently used settings and apply updated styles consistent with recent Form Builder improvements.

• What was solved?

• We reorganized the Menu Block configuration, prioritized essential settings, applied new styles, and reduced the prominence of rarely used options.

Result: Admins can now configure Menu Blocks more efficiently with a cleaner, more intuitive interface.

LHH-22815 – LLS: Reorganize ThemeTypes Order

• What was the issue?

• The theme templates available in the LlamaSite installer were not ordered in the preferred sequence, making it harder for admins to find the most commonly used templates.

• What was solved?

• We reordered the ThemeTypes to reflect the new agreed sequence, placing the most popular templates at the top.

Result: Admins see templates in a more logical, prioritized order during LlamaSite installation.

LHH-22747 – Ability to validate the menu items for the Skills functionality

• What was the issue?

• The Skills functionality's menu items were not included in the HOC4 package manager, meaning they could not be validated or packaged alongside other features like Teams and Self Report.

• What was solved?

• We added the Skills menu items to the package manager with a hidden validation rule, consistent with how Teams and Self Report are handled.

Result: Skills functionality can now be validated and packaged reliably through the package manager.

LHH-22732 – HOC4 CMS, missing link to request portal access

• What was the issue?

• The "Grant Partner Staff Access" link was missing from the My Organizations page in the CMS, preventing partners from easily requesting portal access.

• What was solved?

• We restored the Grant Portal Access link to the My Organizations page.

Result: Partners can once again request portal access directly from the My Organizations page.

LLH4v1.19.1 (Released: 02/25/2026)

Overview

This release fixes issues with user access removal in LlamaSite, a button block configuration problem, and adds Danish language search support.

🐞 Bug Fixes

LHH-22870 – LLS: Removing access to a LlamaSite user is not working

• What was the issue?

• When using the "Remove Access" option in LlamaSite, the system removed access on the Contact record but did not properly update the user's profile in the database. Additionally, no log entries were recorded for this action.

• What was solved?

• We restored the logic in the access-granting controller to properly handle the "Remove Access" scenario (when the profile is set to "None"), ensuring both the Contact and the database are updated consistently.

Result: Admins can now reliably remove user access from LlamaSite, and the change is reflected in both the Contact and the underlying database.

LHH-22860 – Enable Custom Logic Button Does Not Work

• What was the issue?

• When configuring a Button Block in the CMS, the "Enable Custom Logic" checkbox did not respond when clicked—nothing happened after checking the box.

• What was solved?

• We corrected the styles from the new block design that were interfering with the checkbox behavior.

Result: The "Enable Custom Logic" checkbox now works as expected in the Button Block configuration.

🆕 New Features / Enhancements

LHH-22876 – Add configuration in services to use the Danish Solr schema

• What was the issue?

• The search services for opportunities needed to support the Danish language, requiring a new Solr catalog configuration.

• What was solved?

• We updated the search services to use the new Danish Solr catalog ("pda") when the Danish language parameter is received.

Result: Opportunity search results now work correctly for Danish-language sites.

LLH4v1.19.2 (Released: 03/02/2026)

Overview

This release focuses on multi-language support for a global customer (Cycling Without Age), fixes team signup and email update issues, and introduces landing page language localization.

🐞 Bug Fixes

LHH-22868 – Sign up with a team feature needs to be fixed

• What was the issue?

• When a volunteer created a new team during signup, the team was not automatically signed up for the shift—requiring the volunteer to go back and sign up again. Additionally, team members added during signup were not always created or connected, and members with previously declined connections were shown as signed up when they were not.

• What was solved?

• We corrected the team creation and signup flow so that creating a new team during the signup process also registers that team for the selected shift. Team member creation and connection logic was also fixed to handle edge cases including declined connections.

Result: Team signups now work end-to-end: creating a new team during signup registers the team for the shift, and all team members are properly created and connected.

🆕 New Features / Enhancements

LHH-22883 – LLS Automatic Landing Pages (ALP) language localization – Part I

• What was the issue?

• Automatic Landing Pages (ALPs) did not support displaying content in different languages. Content managers had no way to set a specific language for each landing page.

• What was solved?

• We implemented initial language localization support for ALPs, allowing each landing page to use the LLS/HOC language property file to display content in the selected language.

Result: Content managers can now set different languages for each ALP, and visitors see content displayed in their selected language.

LHH-22884 – Add German as a system language

• What was the issue?

• German language support was needed for an upcoming cluster of customer chapters.

• What was solved?

• We enabled German (de-DE) on the customer instance and created an AI-generated translation of the LlamaSite and HOC4 language property files.

Result: The customer's site now supports German as a system language across all LlamaSite and HOC4 interfaces.

LHH-22879 – Add Swedish as a system language

• What was the issue?

• Swedish language support was needed for an upcoming cluster of customer chapters.

• What was solved?

• We enabled Swedish (sv-SE) on the customer instance and created an AI-generated translation of the language property files.

Result: The customer's site now supports Swedish as a system language.

LHH-22878 – Add Dutch as a system language

• What was the issue?

• Dutch language support was needed as an option for the customer's chapters.

• What was solved?

• We enabled Dutch (nl-NL) on the customer instance and created an AI-generated translation of the language property files.

Result: The customer's site now supports Dutch as a system language.

LHH-22872 – Add Danish as a system language

• What was the issue?

• Danish language support was needed for an upcoming cluster of customer chapters.

• What was solved?

• We enabled Danish (da-DK) on the customer instance and created an AI-generated translation of the language property files.

Result: The customer's site now supports Danish as a system language.

LHH-22897 – Create and configure SOLR catalog for German language

• What was the issue?

• A SOLR catalog was needed to support German-language opportunity search.

• What was solved?

• We created and configured a new SOLR catalog ("pde") for the German language.

Result: Opportunity search now works correctly for German-language sites.

LHH-22898 – Create a SOLR Catalog for Swedish language

• What was the issue?

• A SOLR catalog was needed to support Swedish-language opportunity search.

• What was solved?

• We created a new SOLR catalog for the Swedish language.

Result: Opportunity search now works correctly for Swedish-language sites.

LHH-22905 – Search engine should return records for German and Swedish

• What was the issue?

• The search services used for searching opportunities did not support the German and Swedish SOLR catalogs.

• What was solved?

• We updated the search services to use the "pde" catalog for German and the "psv" catalog for Swedish.

Result: Opportunity searches now return accurate results for both German and Swedish language sites.