LLH4v1.18.0 (Released: 02/05/2026)

Overview

This HOC4 release delivers improvements to CMS menu configuration, site template content, system constants in Form Builder, and infrastructure stability. It also removes deprecated listing code and resolves an error affecting opportunity detail pages.

🐞 Bug Fixes

LHH-22677 – Error retrieving the layout from database on Opportunity details

• What was the issue?

• A recurring error ("Object reference not set to an instance of an object") was appearing on opportunity detail pages across multiple sites, caused by a failure in retrieving site images from the database.

• What was solved?

• We corrected the image retrieval logic so that opportunities load reliably even when certain image metadata is missing or unavailable.

Result: Opportunity detail pages now load without errors across all affected sites.

🆕 New Features / Enhancements

LHH-22408 – CMS Menu configuration page UI improvements

• What was the issue?

• The CMS menu editing interface had unclear labels (e.g., "Page:" and "URL:") and lacked a search/type-ahead capability, making it harder for admins to configure menu items efficiently.

• What was solved?

• We updated labels to be more descriptive ("Page or Custom URL/Path:", "URL or Path:"), added a "Custom URL/Path" option, introduced type-ahead search in the page picklist, and concatenated page names with their paths for clarity.

Result: CMS admins can now configure menu items more quickly and with greater confidence about which pages or URLs they are linking.

LHH-22678 – Remove deprecated Listing CMS DataTable code

• What was the issue?

• A deprecated JavaScript function for Listing CMS DataTable rendering was still present in the codebase. Recent enhancements were accidentally being applied to this legacy code instead of the current Listing CMS block implementation.

• What was solved?

• We validated that the deprecated function is no longer in use and removed it entirely, ensuring all future improvements target the correct, current implementation.

Result: Listing CMS blocks now consistently reflect all enhancements, and developers are protected from accidentally updating legacy code paths.

LHH-22697 – Update the copy for the new Modern Version template for LlamaSite installation

• What was the issue?

• The Modern Version template used during new LlamaSite installations needed updated copy to reflect current branding and content standards.

• What was solved?

• We refreshed the content and copy within the Modern Version clonable template.

Result: New LlamaSite installations using the Modern Version template now start with up-to-date, polished content.

LHH-22698 – Generate copy for the new Standard Version template for LlamaSite installation

• What was the issue?

• A Standard Version template was needed for new LlamaSite installations, but the content had not yet been created.

• What was solved?

• We authored and integrated the copy for the Standard Version template.

Result: Customers choosing the Standard Version template now have a clean, ready-to-use starting point for their site.

LHH-22720 – Integrate HOC-Search-Service with the LlamaSiteSalesforceIntegration library

• What was the issue?

• The search service was using HttpClient instances in a way that could cause SNAT port exhaustion issues in production, leading to intermittent connectivity failures.

• What was solved?

• We integrated the search service with the new LlamaSiteSalesforceIntegration library, which uses an improved HttpClient pooling strategy for cleaner, more reliable HTTP connections.

Result: The search service is now more stable and resilient in production, reducing the risk of connectivity-related errors.

LHH-22741 – Allow System Constants in Form Builder

• What was the issue?

• System Constants (per-site configurable values) were only available in listing blocks and could not be used within Form Builder forms. They also weren't included in the packaging manager.

• What was solved?

• We extended System Constants support to Form Builder, allowing form configurations to reference site-level constants. We also enabled System Constants to be included in the packaging manager.

Result: Admins can now use System Constants in both listing blocks and custom forms, and these values carry over during packaging and deployment.

LLH4v1.18.1 (Released: 02/09/2026)

Overview

This release fixes several customer-reported issues related to partner portal operations, signup emails, form workflows, and image rendering. It also adds custom fonts and a new Get Connected template, and addresses an infrastructure stability issue with HttpClient disposal.

🐞 Bug Fixes

LHH-22748 – HOC4 – Unexpected second relationship created for new Contacts

• What was the issue?

• When new contacts were created through Organization Registration in HOC4, a second, unexpected relationship was being added to the source Salesforce Account, causing confusion for partners who saw unknown contacts linked to their organization.

• What was solved?

• We corrected the contact-creation logic so that only the intended relationship to the volunteer's own organization is created—no extra relationship to the source account.

Result: Partners no longer see unexpected contacts appearing on their account, keeping their contact records clean and accurate.

LHH-22767 – Special Directions picture showing up as a broken link

• What was the issue?

• Images inserted into the Special Directions field for a location appeared as broken links on the volunteer confirmation page. The underlying Salesforce field is plain text, so rich-text images were rendered as non-functional URLs.

• What was solved?

• We updated how the Special Directions content is rendered so that images are properly handled regardless of the Salesforce field type.

Result: Volunteers can now see the intended photos and visual directions on their confirmation pages, improving the on-site experience.

LHH-22768 – Partner Portal issues adding a Connection

• What was the issue?

• Partners were unable to add connections to existing opportunities because certain contacts (who had valid volunteer history) were not appearing in the contact lookup.

• What was solved?

• We fixed the list view and lookup logic that powers the contact selection so all eligible contacts are returned correctly.

Result: Partners can now reliably find and add connections to opportunities from the Partner Portal.

LHH-22774 – ARS Login Workflow field update not happening

• What was the issue?

• A hidden field in the ARS Login Workflow was supposed to stamp the current date on submit, but it was not being populated. This caused branch conditions to behave incorrectly, repeatedly redirecting users to the profile update page. Additionally, form logic involving hidden required fields and picklist/radio button values caused further issues.

• What was solved?

• We corrected the form submission logic so that hidden fields are properly saved—even when they involve picklist values and radio buttons—and the date stamp is reliably applied.

Result: The ARS Login Workflow now correctly updates the date field on submit, and branch conditions behave as expected without unnecessary redirects.

LHH-22793 – Two emails being sent for Individually Scheduled Express Interest Only (ISO) signups

• What was the issue?

• Volunteers who signed up via "Express Interest Only" for individually scheduled opportunities were receiving two confirmation emails instead of one. Admins could not identify where the second email was originating.

• What was solved?

• We identified and disabled the duplicate email trigger so that only the intended confirmation email is sent.

Result: Volunteers now receive a single, clear confirmation email after expressing interest in an individually scheduled opportunity.

LHH-22794 – "Cannot access a disposed object" HttpClient error

• What was the issue?

• An HttpClient disposal error was occurring intermittently across multiple services, causing failures in Salesforce API calls (e.g., retrieving managing org info, list views). This affected multiple sites.

• What was solved?

• We resolved the HttpClient lifecycle management issue to prevent premature disposal of active HTTP connections.

Result: API calls to Salesforce are now more reliable, eliminating the intermittent 500 errors caused by disposed HttpClient objects.

🆕 New Features / Enhancements

LHH-22699 – Generate copy for the new Get Connected Template for LlamaSite installation

• What was the issue?

• A Get Connected Version template was needed for LlamaSite installations, but the content had not yet been authored.

• What was solved?

• We created and integrated the copy for the Get Connected template.

Result: Customers choosing the Get Connected Version template now have a polished, ready-to-use starting point for their site.

LLH4v1.18.2 (Released: 02/12/2026)

Overview

This release focuses on bug fixes affecting team signups, multi-shift signups, partner portal dropdown formatting, opportunity creation, ARS login workflows, and CMS menu editing improvements.

🐞 Bug Fixes

LHH-22766 – Error when signing up for multiple shifts at once

• What was the issue?

• Volunteers who tried to sign up for a large number of shifts simultaneously received an error. There was no clear limit communicated, and the error was not handled gracefully.

• What was solved?

• We improved error handling so that when Salesforce limits are reached, the system provides a clear, user-friendly message rather than an unhandled error. The signup is still processed to the extent possible.

Result: Volunteers now receive a helpful message if they exceed the shift signup limit, instead of a confusing error screen.

LHH-22804 – Team signup – team members not appearing or being created

• What was the issue?

• When a volunteer created a new team and added members during the signup process, not all team members appeared on the confirmation page, and some were not properly created. Additionally, the Team Captain was not counted in the total members, and the "My Teams" page did not show the associated volunteer opportunities.

• What was solved?

• We corrected the team creation and member-registration logic so that all added members are properly saved, displayed, and counted—including the Team Captain.

Result: Team signups now work reliably end-to-end: all members appear, totals are accurate, and signed-up opportunities display on the My Teams page.

LHH-22808 –  Admin Portal: Entering Volunteer Opportunity not creating an Occurrence

• What was the issue?

• When certain partners used the Admin Portal to create a volunteer opportunity, the process returned a 500 error and failed to create the required occurrence record.

• What was solved?

• We fixed the custom opportunity-creation flow for this portal so that occurrences are properly generated upon submission.

Result: Partners using the Admin Portal can now successfully create volunteer opportunities with occurrences as intended.

LHH-22810 – Partner Portal Volunteer Opportunity dropdown formatting issues

• What was the issue?

• Dropdown menus in the Partner Portal displayed formatting issues when values contained special characters (such as "&"), showing garbled text. Additionally, an outdated approval message option ("We have approved your record and it was posted 11/9/2011") was still appearing.

• What was solved?

• We fixed the HTML encoding for special characters in dropdown values and removed the outdated approval message option.

Result: Partner Portal dropdowns now display cleanly, and admins see only relevant, current options.

LHH-22813 – ARS Login Workflow field update not happening (follow-up)

• What was the issue?

• Despite a prior fix, the ARS Login Workflow was still failing to update the date field for certain contacts, causing the system to repeatedly present the profile update form.

• What was solved?

• We performed a deeper investigation and resolved the remaining edge case that prevented the hidden date field from being stamped correctly on submission.

Result: The ARS Login Workflow now reliably updates the date field for all contacts, ending the unnecessary profile update redirects.

🆕 New Features / Enhancements

LHH-22775 – UI improvements for Menu Item editing

• What was the issue?

• Several UI inconsistencies were identified in the CMS menu editing mode, making it less intuitive for administrators.

• What was solved?

• We addressed the visual inconsistencies in the menu item editing interface, improving layout, alignment, and labeling.

Result: Admins will find the menu editing experience more polished and consistent.

LLH4v1.18.3 (Released: 02/16/2026)

Overview

This release introduces an SSO configuration option for controlling assertion data behavior and adds support for the LlamaSite AI Assistant in the US Central instance.

🐞 Bug Fixes

This release is focused solely on enhancements and does not include bug fixes.

🆕 New Features / Enhancements

LHH-22839 – SSO setting to control whether SAML assertion data overrides existing Contact information

• What was the issue?

• When SSO is configured with Salesforce as the Identity Provider (IDP), the SAML assertion data could overwrite existing contact information—even when the Salesforce user record had different data than the related contact. Admins had no way to prevent this override behavior.

• What was solved?

• We added a new SSO configuration setting that lets admins control whether assertion data should override existing contact information or leave it intact.

Result: Admins can now choose to preserve existing contact data during SSO login, which is especially important when Salesforce is the IDP and user data may differ from the associated contact record.