HOC Release Notes 3.12.12 (Mar 06 - Mar 18)

New Features:

Improved Listing Block Faceting (LHH-20423)

This update introduces a new feature to the Listing Block, allowing CMS administrators to control the display of facets. Previously, facets would show all available options, even if some had zero associated records.

Now, a new setting has been added to the facet configuration that enables the ability to hide options that have no records referenced. This provides a cleaner and more relevant filtering experience for users.

Deployment to Production: March 6, 2025.

Centralized CMS Versioning List (LHH-20877)

This update introduces a new feature to centralize and display a list of recent changes related to blocks and pages for each site within the Content Management System (CMS). This provides administrators with a clear overview of the most recent updates.

You can access this new functionality in the new CMS via the menu option: Content > Version List. This initial version allows you to view the version list and access the configuration for selected items.

Deployment to Production: March 11, 2025.

Improvements:

Resolved: "Volunteer" as Last Name in Registration Forms (LHH-20796)

This update addresses an issue where users were frequently entering "Volunteer" as their last name during portal account creation, likely due to example text in the registration form. This was particularly noticeable in HOC3 environments.

To improve usability and prevent this common input error, the following changes have been implemented:

  • HOC3 Registration Forms: Placeholders (example text) for "Name," "First Name," and "Email Address" fields have been removed. This aims to reduce confusion and improve accessibility, as these fields are self-explanatory and the previous placeholders were not tagged for screen readers.
  • HOC4 Registration Forms: No changes were made, as custom forms in HOC4 are dynamically configured and do not set placeholders by default for "Name," "Last Name," and "Email Address."
  • HOC3 Telephone Placeholder: Fixed telephone placeholders have been replaced with the intlTelInput plugin's dynamic placeholders. These dynamic placeholders align with input validation logic, improving consistency and reducing potential user confusion.

These changes are based on best practices regarding form design, which suggest that placeholders should be supplementary and, if used, properly accessible. Removing confusing placeholders is expected to enhance the user experience across both HOC3 and HOC4.

Deployment to Production: March 6, 2025.

Multi-Sign Up Button Text Update (LHH-20878)

This update resolves a minor usability issue during multi-shift sign-ups. Previously, the confirmation button read "Send," which could be confusing.

The button text has been updated to "Yes," providing a clearer and more intuitive confirmation for users signing up for multiple shifts.

Deployment to Production: March 6, 2025.

Blocks Now Include "Authorized For" Setting and Logged-In User Visibility (LHH-20879)

This update enhances the functionality of various CMS blocks by introducing the "Authorized For" setting, previously seen in the Featured Opportunity Block. This setting allows administrators to control who can view specific blocks.

Specifically, the HTML and Button blocks now include the "Authorized For" setting. Additionally, all blocks now have the ability to be configured for visibility. This provides greater control over content access and personalization for your website.

Deployment to Production: March 6, 2025.

Resolved: Team Registration Without Captain (LHH-20876)

This update resolves a critical issue where, in projects requiring an adult (18+) for registration and allowing minors to join only as part of an adult's team, adults/team captains were able to drop out of a project, leaving underage volunteers still registered. This posed significant issues for nonprofit partners, including supervision and liability concerns.

The problem occurred because the restriction on adults dropping out and leaving minors registered was only implemented on the public-facing site, and was missing in the mobile application.

To address this, a validation has been added at the web service level. This ensures that the restriction is handled universally, preventing adults/team captains from removing themselves and leaving underage volunteers behind, regardless of whether they are using the public site or the mobile app.

Deployment to Production: March 6, 2025.

New CMS Layout Issues Resolved (LHH-20906)

This update resolves several issues encountered in the new Content Management System (CMS) layout, improving usability and functionality for administrators.

Specifically, the following have been addressed:

  • Menu Item URL Exclusion: You can now correctly specify URLs to exclude in a menu item.
  • Custom Field Saving: The issue preventing the saving of custom fields in the new CMS layout has been resolved.

Deployment to Production: March 11, 2025.

Fix for Activity/Opportunity Calendar Filters and New CMS (LHH-20908)

This update resolves issues related to filters in the activity and opportunity calendar. Previously, filters were not displaying correctly, and the new CMS layout was missing the "+" button for showing more records, a feature available in the old layout.

The cause was identified as missing validations for the new CMS layout. The fix includes:

  • Adding the missing logic for the new CMS layout, ensuring that filters display correctly and the "+" functionality is restored.
  • Adding help text to clarify the relationship between fields on the public site and Salesforce fields, specifically addressing issues where new "Activity Type" values were not appearing because they were added to the wrong Salesforce field (HOC__Activity_Type__c instead of HOC__Volunteer_Activity_Type__c).

These changes ensure a more functional and user-friendly experience when managing activity and opportunity calendars in the new CMS.

Deployment to Production: March 11, 2025.

Special Directions" HTML Field Now Clickable (LHH-20922)

This update resolves an issue where links within the "Special Directions" HTML field were clickable in Salesforce but not on the public-facing website.

A feature has been implemented to convert URLs into clickable links within the content of the "Special Directions" field, ensuring that these links are now fully functional on the website.

Deployment to Production: March 18, 2025.

0 Comments

Add your comment

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.