LLH4v1.24.0 (Released: 04/30/2026)

Overview

This release fixes Packaging Manager modal Form ID mapping, search results not redirecting after login for authenticated pages, PostInstall ExecApex service errors, volunteer tile spots display, account/organization creation missing matching rules, form cancel button not saving, and account registration errors. It also adds Check-In Kiosk ID Badge printing, alphabetical ordering of Partner Portal Opportunity Coordinators, unified Spanish translations for Salesforce reports, improved error messaging for multiple edits in listing blocks, CWA mobile experience improvements, PostInstall Manager execution logging and security review, package manager license expiration date validation fixes, custom font installation, SOQLs for Person-to-Person chat forms, WAF log review for false positives, and continued work on the SF Metadata Migrator tool (Part V).

🐞 Bug Fixes

LHH-21452 – Packaging Manager Installation Does Not Update Form IDs in Modals

• What was the issue?
• When installing a Packaging Manager Package (PMP), modal components (e.g., in Listing CMS blocks) retained hardcoded Form IDs from the source org. Instead of being updated to match the target Public Site's forms upon installation, the modals continued referencing the original Form IDs, causing them to load incorrect or non-existent forms.
• What was solved?
• We updated the Packaging Manager installation process to detect and update Form IDs referenced within modal component configurations, ensuring they are properly mapped to the corresponding forms in the target Public Site.

Result: Modal components in Packaging Manager packages now correctly reference the target site's Form IDs after installation.

LHH-23166 – Authenticated Page URL Not Redirecting After Login (Critical)

• What was the issue?
• When volunteers clicked a URL to an authenticated page (e.g., a survey link sent via email), the system prompted them to log in but did not redirect them to the intended page afterward.
• What was solved?
• We corrected the post-login redirect logic to properly preserve and use the original URL as the redirect target after successful authentication.

Result: Users clicking links to authenticated pages are now properly redirected to the intended page after logging in.

LHH-23279 – Volunteer Tile Displaying "0 Spots Available" When Spots Exist

• What was the issue?
• Volunteer opportunity tiles on the search page were incorrectly displaying "0 spots available" even when spots were actually available, misleading volunteers into thinking opportunities were full.
• What was solved?
• We corrected the spot availability calculation logic in the volunteer tile display to accurately reflect the number of available spots.

Result: Volunteer tiles now correctly display the actual number of available spots.

LHH-23285 – Custom Forms Cancel Button Not Saving Configuration

• What was the issue?
• When enabling the Cancel button on a form's submit configuration (e.g., Partner Portal Edit Opportunity), the setting would not save. Users could toggle the option, but the configuration was not persisted.
• What was solved?
• We fixed the form configuration save logic to properly persist the Cancel button settings on submit buttons.

Result: Cancel button settings on custom forms now save correctly.

🆕 New Features / Enhancements

LHH-23164 – Check-In Kiosk ID Badge Printing

• What was the issue?
• Volunteer coordinators had no way to print visitor ID badges when volunteers checked in via the HOC4 Check-In Kiosk. This feature was needed for organizations  that require visible identification for on-site volunteers.
• What was solved?
• We implemented an ID Badge printing feature for the Check-In Kiosk that supports:
  • Configurable badge content including logo, volunteer name, role, team name, and company
  • Badge printing on thermal label printers (e.g., Zebra ZP450/LP2844) with dimensions approximately 3.5" × 2.25"
  • Salesforce picklist fields on Contact and Volunteer Opportunity/Occurrence to control whether badges are required
  • Ability to select and configure printers from the kiosk, with support for multiple kiosks sharing or using different printers
  • Flexible badge layout using customizable HTML templates

Result: Volunteer coordinators can now print ID badges automatically during kiosk check-in when "ID Badge Required" is set to "Yes."

LHH-22827 – Partner Portal Opportunity Coordinators Listed Alphabetically with Smart Defaults

• What was the issue?
• In the Partner Portal, the list of Opportunity Coordinators was not sorted in any order, making it difficult to find specific coordinators. Additionally, when creating an occurrence from an opportunity, the coordinator selected on the parent opportunity was not pre-selected as the default.
• What was solved?
• We alphabetized the Opportunity Coordinator dropdown list and implemented smart defaulting so that the coordinator assigned to the parent opportunity is pre-selected when creating a new occurrence.

Result: Opportunity coordinators are now listed alphabetically, and the coordinator defaults to the parent opportunity's selection on the occurrence page.

LHH-22819 – Unified Spanish Report Column Titles

• What was the issue?
• Reports displayed on the Partner Portal contained a mix of English and Spanish column titles, making them harder to read and interpret for Spanish-speaking users.
• What was solved?
• We updated the Salesforce reports so that all field labels and column titles are consistently in Spanish across all reports displayed on the portal.

Result: All reports on the portal now display column titles consistently in Spanish.

LHH-23194 – Matching Rules for Account/Organization Creation in HOC4

• What was the issue?
• HOC4 was missing the matching rules that existed in HOC3 for organization creation. This allowed duplicate organizations to be created and primary/secondary contacts to be duplicated rather than reused.
• What was solved?
• We implemented the following matching rules in HOC4:
  1. Organization name must not be duplicated
  2. The primary contact must not be a primary contact in any other organization
  3. The secondary contact must not be a primary contact in any organization
  4. If primary or secondary contacts already exist, those records are reused

Result: Account/organization creation in HOC4 now enforces the same duplicate prevention and contact reuse rules as HOC3.

LHH-23197 – Improved Error Messaging for Multiple Edits in Listing Blocks

• What was the issue?
• When performing multiple record updates from a listing CMS block with edit mode enabled, raw technical error details were passed directly to the user. If the same error occurred for multiple records, it was displayed redundantly.
• What was solved?
• We improved the error message formatting to remove technical details and display user-friendly messages. Duplicate errors for multiple records are now displayed only once.

Result: Error messages during multiple edits in listing blocks are now cleaner, non-technical, and deduplicated.

LHH-23134 – Mobile Experience Improvements

• What was the issue?
• Mobile experience improvements were added to better serve users accessing the platform from mobile devices.
• What was solved?
• We implemented the mobile changes improving layout and usability on mobile devices.

Result: Sites now provide an improved experience for mobile users.

LHH-23254 – Package Manager License Expiration Date Validation Fix

• What was the issue?
• An LLS License with an expiration date of 04/26/2026 in both Mothership and the database was incorrectly displayed as expired on 04/21/2026 — five days before the actual expiration date.
• What was solved?
• We corrected the expiration date validation logic to accurately compare the current date against the license expiration date, accounting for timezone differences.

Result: Package Manager licenses now correctly show as active until their actual expiration date.

LHH-23255 – Custom Font Installation

• What was the issue?
• A customer provided custom font files (United Sans Condensed and Acumin) that needed to be uploaded and made available in the CMS.
• What was solved?
• We installed the custom fonts in the CMS, making them available for use in site styling and code injection.

Result: United Sans Condensed and Acumin fonts are now available in the CMS for customer use.

LLH4v1.24.1 (Released: 05/07/2026)

Overview

This hotfix release resolves duplicate session variable addition in Header Logo and Sponsor blocks, zip code search accuracy issues, Google sign-in errors, and team signup not adding members to shifts. It also includes production testing and improvements for the ID Badge feature.

🐞 Bug Fixes

LHH-23112 – Header Logo and Sponsor Blocks: Session Variables Added Twice

• What was the issue?
• In the Header Logo and Sponsor block configurations, clicking the "Add" button for session variables in custom rules would add the variable twice instead of once, creating duplicate entries.
• What was solved?
• We corrected the button handler to prevent duplicate additions, ensuring session variables are added only once per click.

Result: Session variables are now added exactly once when using the Add button in Header Logo and Sponsor block configurations.

LHH-23274 – Zip Code Search Not Returning Accurate Results

• What was the issue?
• Searching with certain zip codes (e.g., 90210) returned no results, while other zip codes (e.g., 90001) worked correctly. The search results were inaccurate for specific zip codes.
• What was solved?
• We investigated and corrected the zip code geocoding/search logic that was causing certain valid zip codes to return empty or inaccurate results.

Result: Zip code-based searches now return accurate results for all valid zip codes.

LHH-23309 – Google Sign-In Error on Public Site

• What was the issue?
• Volunteers were unable to sign in to the public site using Google sign-in. After authenticating with Google, the redirect back to the site produced an error, preventing access. The issue was reported by multiple volunteers.
• What was solved?
• We resolved the error in the Google OAuth callback processing that was causing the redirect failure after Google authentication.

Result: Google sign-in now works correctly, and volunteers can access the site using their Google accounts.

LHH-23330 – Team Signup: Adding Team Member to Shift Does Nothing

• What was the issue?
• When a team captain attempted to add a team member to an existing shift signup, the action appeared to complete successfully but the team member was not actually added. The UI showed success feedback, but the registration was not saved to Salesforce.
• What was solved?
• We fixed the team member addition logic to properly process and save the registration when adding team members to shifts that already have existing team signups.

Result: Team captains can now successfully add additional team members to shifts, and the registrations are properly saved.

🆕 New Features / Enhancements

LHH-23296 – ID Badge Production Testing and Improvements

• What was the issue?
• The ID Badge printing feature introduced in v1.24.0 needed production testing and evaluation for necessary improvements based on real-world usage.
• What was solved?
• We conducted production tests of the ID Badge feature, identified areas for improvement, and implemented the necessary enhancements to ensure reliable badge printing in production environments.

Result: The ID Badge printing feature has been validated in production and refined based on testing feedback.

LLH4v1.24.2 (Released: 05/12/2026)

Overview

This hotfix release resolves CMS listing results not displaying on the "my-teams-page" and includes custom font installation for OBK (0392).

🐞 Bug Fixes

LHH-23339 – CMS Listing Results Not Displaying on "My Teams" Page

• What was the issue?
• CMS listing results were not displaying for certain elements on the "my-teams-page." The page failed to render expected listing data, leaving users unable to see their team information.
• What was solved?
• We identified and corrected the issue preventing listing results from rendering on the "my-teams-page," restoring the expected display of team-related data.

Result: All CMS listing elements on the "my-teams-page" now display results correctly.

🆕 New Features / Enhancements

LHH-23358 – Custom Font Installation for OBK.

• What was the issue?
• OBK needed custom fonts applied as part of their branding, design, and look & feel configuration.
• What was solved?
• We installed and configured the custom fonts for OBK's site to match their branding specifications.

Result: OBK's site now uses the specified custom fonts consistent with their brand guidelines.