HOC3v13.1.8 (Released: 05/05/2026)

Overview

This release fixes an auto-suggest issue on dependent picklist fields that prevented value selection, resolves a code injection save error on a specific page, and adds expiration-based persistence to calendar/search filters so they no longer persist indefinitely across sessions.

🐞 Bug Fixes

LHH-23056 – Auto-Suggest Not Allowing Value Selection on Dependent Picklist Field

• What was the issue?

• The auto-suggest feature on a dependent picklist field was not allowing values to be selected. Users could see suggestions but could not select them, preventing form completion. This was the same class of issue previously addressed in HOC4 (LHH-23142) where auto-suggest interfered with dependent picklist behavior.

• What was solved?

• We corrected the dependent picklist field logic so that auto-suggest works properly with dependent fields, allowing values to be selected as expected.

Result: Volunteers can now select values from dependent picklist fields with auto-suggest enabled.

LHH-23163 – Error When Saving Code Injection on Specific Page

• What was the issue?

• When editing and saving the code injection on a specific CMS page, an error occurred and the changes were not saved. The issue was isolated to a particular page's code injection configuration.

• What was solved?

• We reviewed the case and applied JavaScript adjustments to correct the save behavior for code injection on the affected page.

Result: Code injection can now be saved successfully on the previously affected page without errors.

LHH-23277 – Calendar Page Search Filters Persisting Indefinitely Across Sessions

• What was the issue?

• On the calendar page, search filters applied by a user persisted indefinitely — even after navigating away, closing the browser, or logging out and back in. Unlike the regular search page where filters reset, the calendar page retained previous filter selections across sessions, forcing users to manually clear them each time they returned.

• What was solved?

• We implemented expiration-based persistence for calendar and search filters in browser storage, aligned with the regular search page behavior. Key changes include:
  • Introduced a global retention setting (SEARCH_FILTER_EXPIRATION_DAYS, default 7 days) to control filter lifetime in one place.
  • Added metadata-backed storage (createdAt, updatedAt, expiresAt) with lazy backfill for legacy entries that had no metadata.
  • Expired filter values now reset to defaults on read, preventing reuse after expiration.
  • Prevented first-load auto-renewal so expired filters are not unintentionally revived by simply opening the page.
  • Explicit user reset/clear actions remain unchanged and immediate.

Result: Calendar page search filters now automatically expire after 7 days (configurable), matching the behavior of the regular search page. Users returning to the calendar page after the retention period will see a clean, unfiltered view.

🆕 New Features / Enhancements

This release is focused solely on fixes and does not introduce new features.