We've fixed several bugs related to the management of team signups by a team captain related to the setting for registration cutoff hours in the occurrence.

1) Team captains could not remove their team if the cutoff deadline had passed.  They were also not able to remove themselves or individual team members after the cutoff deadline was reached.  They'll now be able to remove their team or any team members anytime up to the start of the opportunity.  

2) Team captains were able to add additional team members to an occurrence after the cutoff deadline had passed.  Team captains will no longer be able to add addition team members after the cutoff hour deadline has been reached.

In some summary reports viewed in the sharing portal, the column headings weren';t lining up with the actual columns, making it difficult to read and understand the reports.  (Headers were shifted to the left).  This has been corrected!

A rare bug was fixed wherein a sharing portal user, whose age in their contact record was less than the minimum age for an opportunity, was unable to administratively create connections for ISO-EIO opportunities.  This has been corrected.

Salesforce doesn't go down much, but when it does, search was no longer able to return opportunity detail (because the data was pulled directly from Salesforce).  This can cause problems even if Salesforce is briefly unavailable.    To address this, our search server (SOLR) now will have the most recent versions of opportunity details so that even if Salesforce is temporarily offline, opportunity detail pages will still display.

A rare bug was discovered when using the check-in kiosk with guest registration active, for an occurrence that was part of a grouped occurrence.  An error message prevented the guest from checking in.   The reason was - when a guest checks in the connection is made in 'attended' status, however, because the occurrence is 'grouped' - additional connections for future dates are made, and these cannot be marked as attended because they haven't taken place yet.  

Here's the corrected behavior that will take place IF a guest checks in for an occurrence that is part of a grouped occurrence.
1) A connection for that day's occurrence will be made and marked attendance.
2) Connections will automatically be made for the remainder of the grouped occurrence, but these will be in 'please verify' attended status.

This will prevent an error message from preventing guest check-in - but will have the consequence of signing up a guest for multiple occurrences.