LLH4v1.20.0 (Released: 03/04/2026)

Overview

This release addresses critical bugs including a CMS crash caused by image blocks, connection email notification overrides, cover image upload errors, and volunteer opportunity search issues with special characters. It also continues ALP language localization work, introduces redesigned CMS block layouts, adds custom font support, resolves a customer's service configuration errors, and completes a data migration task.

🐞 Bug Fixes

LHH-22932 – CMS Down After Creating New Image Block

• What was the issue?

• A customer created a new image block named "Wave" in the CMS, and upon saving it the platform crashed, returning a 500 error on all public-facing pages. The CMS was completely inaccessible.

• What was solved?

• We identified and resolved the issue in the image block save process that caused the CMS to crash, restoring full access to all public-facing pages.

Result: Creating and saving image blocks no longer causes the CMS to crash. All public-facing pages load correctly.

LHH-22933 – Connection Email Notifications Not Respecting Settings

• What was the issue?

• When email notifications (such as the post-opportunity email) were turned off for a specific occurrence, volunteers still received those emails. The notification override settings were not being respected.

• What was solved?

• We corrected the email notification logic so that when email notifications are disabled at the occurrence level, the system properly suppresses those emails.

Result: Email notification settings on occurrences are now honored, and volunteers will not receive emails that have been turned off.

LHH-22908 – 500 Error When Updating Cover Images

• What was the issue?

• Customers were encountering a 500 error when trying to update cover images on their site.

• What was solved?

• We identified and resolved the server-side error that occurred during cover image uploads.

Result: Cover images can now be updated without encountering errors.

LHH-22899 – Volunteer Opportunities Not Displaying Due to Special Characters

• What was the issue?

• When an organization's name contained special characters (such as "&"), the link to view their volunteer opportunities returned no results, even though opportunities existed. For example, "The Robotics Education & Competition Foundation" showed no opportunities until the ampersand was removed.

• What was solved?

• We updated the search and linking logic to properly handle special characters in organization names so that opportunities display correctly regardless of the characters used.

Result: Volunteer opportunities now display correctly for organizations with special characters in their names.

LHH-22873 – Services for Customer 0143 Referencing Incorrect Objects

• What was the issue?

• The services for customer 0143 were incorrectly referencing HOC3 Salesforce objects (e.g., HOC__Connection__c), which are not available on their instance. This caused errors in the logs related to DescribeSObject, GetSalesforceFieldsView, and SelectBySingleResponseUniqueItem.

• What was solved?

• We corrected the service configuration for customer 0143 to reference the proper objects, eliminating the Salesforce integration errors.

Result: The customer's services now reference the correct objects, and the Salesforce integration errors have been resolved.

🆕 New Features / Enhancements

LHH-22921 – Automatic Landing Pages (ALP) Language Localization – Part II

• What was the issue?

• The initial ALP localization (Part I) provided basic language support, but additional work was needed to fully support dynamic content translation and ensure each landing page reliably displays content in the selected language.

• What was solved?

• We continued the localization implementation, refining how the LLS/HOC language property file is used to display ALP content in the chosen language.

Result: Content managers can now more reliably set different languages for each Automatic Landing Page, with improved translation coverage across all dynamic content.

LHH-22904 – Feasibility of Using AI for Translations

• What was the issue?

• With the growing need to support multiple languages, the team needed to evaluate the feasibility of using AI or other automated tools to generate translations efficiently.

• What was solved?

• We completed a feasibility assessment for using AI-based tools to generate language property file translations, confirming a viable approach for rapid multi-language support.

Result: A validated approach for AI-assisted translations is now in place, enabling faster rollout of new language support.

LHH-22857 – New Block Layout – Sponsors Block Settings

• What was the issue?

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

• What was solved?

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

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

LHH-22856 – New Block Layout – Search Result Block

• What was the issue?

• The Search Result Block configuration screen needed a design refresh to align with the updated CMS block layout standards.

• What was solved?

• We redesigned the Search Result Block configuration screen, reorganizing settings by priority and applying the new consistent styles.

Result: The Search Result Block settings are now easier to navigate and configure.

LHH-22855 – New Block Layout – Basic Search Block

• What was the issue?

• The Basic Search Block configuration screen needed updating to match the new block layout design standards.

• What was solved?

• We redesigned the Basic Search Block configuration, prioritizing frequently used settings and applying the updated visual styles.

Result: The Basic Search Block settings now have a cleaner, more intuitive layout.

LHH-22875 – Configure Processing and Storage of Danish Opportunities

• What was the issue?

• Following the addition of Danish as a system language, the opportunity processing and storage system needed to be configured to handle Danish-language opportunities using the pda SOLR catalog.

• What was solved?

• We implemented the necessary configuration to process and store Danish opportunities using the designated SOLR catalog.

Result: Danish-language opportunities are now properly processed and stored for accurate search results.

LHH-22734 – Add Custom Fonts to Site

• What was the issue?

• A customer needed additional custom fonts added to their LlamaSite to match their branding.

• What was solved?

• We added the requested fonts to the site's font library.

Result: The customer's site now supports the additional branded fonts across all CMS pages and blocks.

LHH-22729 – Move Images to the New Container

• What was the issue?

• A customer's images and file upload records needed to be migrated from an old blob container to the correct HOC4 blob container to ensure consistency and proper access.

• What was solved?

• We migrated all images and file upload records from the legacy container (0088) to the correct HOC4 container (10002bd).

Result: All images and uploaded files now reside in the correct storage container, ensuring proper access and display.

LLH4v1.20.1 (Released: 03/10/2026)

Overview

This release fixes language tab switching in CMS block settings and a timezone issue when adding connections. It also adds multi-language translation support for static data counters and improves user deletion handling in LlamaSite.

🐞 Bug Fixes

LHH-22968 – Language Tabs Not Working in Search Result Block Settings

• What was the issue?

• When configuring the Search Result Block in the CMS, the language tabs were not switching correctly, preventing admins from entering translations for different languages.

• What was solved?

• We corrected the tab switching behavior so that language tabs properly display and allow input for each configured language.

Result: Admins can now switch between language tabs in the Search Result Block settings and enter translations as expected.

LHH-22954 – Incorrect Timezone When Adding a Connection

• What was the issue?

• When a partner added a connection through the Partner Portal, the timezone displayed on the connection did not match the opportunity's actual timezone, causing confusion about the correct date and time.

• What was solved?

• We corrected the timezone handling so that connections accurately reflect the opportunity's configured timezone.

Result: Connections now display the correct timezone matching the opportunity, eliminating scheduling confusion.

🆕 New Features / Enhancements

LHH-22928 – Content Translation for Static Data Counter in Listing CMS Settings

• What was the issue?

• In the "Listing CMS Settings" block, when configured in Counter mode with Static Data, there were no fields to enter values in different languages—unlike other blocks that supported multi-language input.

• What was solved?

• We added language-specific input fields to the Static Data Counter configuration, matching the multi-language support available in other CMS blocks.

Result: Content managers can now enter translated values for static data counters in each configured language, ensuring a consistent localized experience.

LHH-22871 – User Deletion Session Update Returns Incorrect Message

• What was the issue?

• When a Contact was deleted from LlamaSite and the DeleteUserLlamaPi.UpdateSession service was called, it returned the message "The contact is not deleted" even though the Contact had already been successfully removed.

• What was solved?

• We corrected the session update logic to properly recognize when a Contact has been deleted, returning an accurate status message.

Result: The system now correctly confirms Contact deletions during the session update process, eliminating misleading error messages.