HOC 3.0.8.2.x Releases (May 2 - May 8, 2019)

This release includes improvements to public security to combat the increased agressiveness of the occasional bot attacks some clients have experienced.  Bug fixes include handling special characters when they appear in a team name, and addressing some occasional errors that occur as a result of incomplete or corrupted data.  Here's some other notable bug fixes and improvements in this release:

Improvement to User Experience (UX) when encountering a 403 error page (HOC3-9185)

CMS Pages that require the user to be logged in, cannot be accessed if you're not logged in.  (Makes sense right?).  Well, if you were to manually enter the URL for a page that requires you to be logged in, the result would be a page that showed that you encountered a 403 error.  Since most users wouldn't know what a 403 error is - this error has been changed so that instead of seeing an error code, the user will be shonw a message "Please login to access this page".  

This page will now also provide the option to login.  If the user then logs in to their account - they will be redirected to the page they were originally trying to access.

Ability to edit the introductory text of the personal information page on public site (HOC3-8279)

The System Page, "Personal information"  /volunteer-personal-Information now includes the ability to edit the introductory text at the top of the page

This can be edited in the CMS by going to Blocks / System Forms / Personal Information.  (You can also rename the section headers here).  Left blank, the default text and header names will continue to be displayed.

Bug Fix:  Unexpected display of Chinese Characters in Grid View Calendar Page (HOC3-9369)

Some clients, who were using the Search Results Block in Calendar display format were seeing Chinese characters appearing next to the date.  This has been fixed.

Bug Fix:  Add to Calendar not adjusting for time zone for Outlook Desktop (HOC3-9384)

In the previous release, the 'add to calendar' functionality was updated to support organizations that listed opportunities in multiple time zones, by using the location of occurrences as the criteria for determining what time zone the calendar files should be set to.  

The Outlook Desktop calendar did not recognize the time zone specific information included in its file.  This has been corrected.  The file for adding to outlook desktop calendar has been recoded so that it populates the correct time in an Outlook calendar.  (Note:  Do not use the ICAL file to add to an Outlook calendar.   Use the file designated for Outlook Desktop).

0 Comments

Add your comment

E-Mail me when someone replies to this comment