v18.2 Release Notes

  • Core: Fixed an issue where Phone Number attributes on the Family Pre-Registration block displayed a JSON string before a name was entered, ensuring the field now shows the correct phone number input box.

  • Core: Fixed an issue where newly added Obsidian block types could fail to appear in the Page Zone Editor after initial startup.

  • Communication: Fixed an issue where the Simple Communication Entry block showed a "Node cannot be null or undefined" error when sending a communication using a template without making any changes. The message was sent successfully, but the error caused unnecessary confusion. This fix prevents the error from appearing in that situation.

  • Core: Fixed an issue where the Attribute Editor did not correctly save configuration changes when creating an Attribute designed to store other Attributes (e.g., an Attribute of type Attribute). This affected scenarios such as defining filters in the Page Parameter Filter block.

  • Group: Fixed an issue in the Group List block where re-adding an archived individual did not allow the option to restore their previous Group Member record and created a new record instead.

  • Communication: Fixed an issue where the "Command Timeout" setting in the Send Group Schedule Notifications Job was not applied correctly, which could cause failures when sending scheduling reminder Communications.

  • CMS: Fixed a security issue affecting multiple blocks that interact with Content Channels, where individuals with only View permissions could delete content items. The delete option is now correctly limited to those with Edit access.

  • CMS: Fixed a display issue in the Obsidian Signature Document List block, affecting the Document column.

  • Core: Fixed an issue where an expiration date on a Person Signal could not be cleared once it was set.

  • Finance: Fixed an issue where the "Move Transactions To Batch" option was incorrectly displayed on the Transaction Details tab of the Transaction List block. This option should only appear when viewing the main Transaction list, not individual Transaction Details.

  • Core: Improved the Attendance History block to work better on small devices such as phones by providing the attendance date as well.

  • Core: Updated several blocks using the Cloudflare Captcha component to ensure consistent and standardized UI behavior.

  • Reporting: Fixed an issue where Reports were unable to be created on the Group entity type.

  • Group: Fixed the behavior of the Group Tree View "Search" feature to use an optional configured Search Result Page (under Advanced settings) instead of the default Group Search Results page.

  • CMS: Fixed issue that prevented adding custom fields to content collection sources.

  • Group: Improved the Obsidian Group Placement Block with person-filtering options, including Gender, Campus, Age, Grade, and Persisted Data View filters.

  • Reporting: Fixed an issue in the Obsidian Dynamic Data block where selected rows were not correctly passed to the Workflow when using the "Launch Workflow" action.

  • Group: Fixed the Group Detail Lava block to exclude inactive Group Members from appearing in the "Leaders" section of the header. These individuals will still appear in the "Inactive Members" section so you can continue to see a complete list of members.

  • Group: Fixed an issue where the GroupFinder block's map markers would not display unless a Google Map ID was used to define the map style.

  • Core: Fixed an issue where Login History entries for individuals authenticated through the Phone Number Lookup block were incorrectly attributed to the wrong Username and Authentication Provider. These records now correctly show the phone number used and properly reflect how the individual signed in.

  • Core: Updated the System Information block to keep the routes table from extending beyond the modal.

  • Lava: Fixed an issue where detail blocks that are loaded in Auto-Edit mode could display outdated information after changes were saved and the individual returned to the block. This occurred when navigating away and then back, causing the block to show pre-update data instead of the most recent changes. The block now correctly refreshes to show current values.

  • CMS: Fixed an issue that caused the wrong theme type to be displayed after cloning a theme until the Rock server rebooted.

  • API: Fixed an error that prevented the Workflows Action Launch API endpoint from functioning.

  • Reporting: Fixed an issue in the Obsidian Dynamic Data block where the Communication Recipient Fields setting was not being applied correctly. Instead of using the specified fields to determine the communication recipients, it always chose the first Person field found in each row. This fix ensures the correct recipients are chosen based on the block setting. Read this Tech Bulletin item for more details on changes to the Dynamic Data Block Person Report.

  • Core: Fixed navigation bar rendering bug: last page link was cut off on small screens.

  • Check-in: Fixed issue that allowed archived groups to be considered valid for check-in. Once a group is archived, it will no longer be available for check-in - including overrides.

  • Lava: Fixed a typo in the Text Box (textbox) LavaShortcode documentation and corrected the Checkbox List (checkboxlist) LavaShortcode's isrequired parameter. Previously, it always evaluated as true, causing the required validation message to appear even when not intended.

  • Finance: Fixed an issue in the TransactionList block where the Show Account Summary setting was being ignored.

  • Event: Fixed an issue where manually added registrants to an Event Registration from the internal portal did not update an existing Group Member’s status according to the Registration Template’s Group Member Status setting.

  • Engagement: Fixed an issue where a Step Program that had system Step Types could still be deleted.

  • Lava: Fixed an issue where saving a Lava Shortcode on the Lava Shortcode Detail page would incorrectly display an error message, even though the shortcode saved successfully.

  • Communication: Fixed an issue where, when editing an RSVP block in the Email Editor, the selected RSVP group was not shown in the settings panel.

  • Communication: Fixed an issue in the Communication Entry Wizard where the Email Performance Analytics To Me toggle label was reversed, causing its Yes/No text to display incorrectly.

  • Communication: Fixed an issue in the Obsidian Communication Entry block where emails composed on iOS Safari would sometimes omit the final line of the message. This happened on iPhones and iPads due to a timing conflict between the form submission and when the message field lost focus.

  • Communication: Fixed an issue where Schedule Reminder emails were being sent after a scheduled occurrence had already ended.

  • Group: Fixed an issue where a group member requirement that falls into a “Warning” state after previously being “Met” was still displayed as “Met” on the Group Member Detail page.

  • Workflow: Fixed an issue that could cause the Send Email workflow action to use an old e-mail address. This could happen under very specific workflow configurations where a Person is accessed in the workflow by certain actions, then a Form action with Person Entry runs and modifies the e-mail address, and finally the Send Email action runs.

  • CRM: Fixed an issue where Family Pre-Registration would incorrectly save a family's address when only a default state was selected by the system, without any other address details entered. This occurred due to the "Enable Default Address State Selection" setting pre-filling the state, causing Rock to treat the address as valid.

  • Check-in: Fixed an issue that caused the Supervisor Login screen in Next-gen Check-in to show invalid groups in the 'Current Counts' section.

  • Security: Improved security by adding HMAC authentication to encrypted string values to ensure data integrity.

  • Lava: Improved the RenderLavaEndpoint command to parse the querystring in the route parameter.

  • Finance: Fixed an issue where creating a Benevolence Request from a Person Profile did not automatically associate the current person, requiring the individual to be manually selected after the request was created.

  • Prayer: Add showBlankItem to CampusPicker in PrayerRequestDetail to stop selecting first campus by default and stop forcing campus selection when campus is not required.

  • Communication: Fixed an issue where Communications submitted through the Communication Entry Wizard block were auto-approved despite exceeding the Maximum Recipients setting. This update ensures that such Communications are routed to an authorized approver and not auto-approved by the sender or other non-approvers.

  • Communication: Fixed the Button block in the Email Editor to allow Lava expressions in the URL field, consistent with the legacy builder. Lava is now resolved when the message is sent, enabling dynamic, personalized links.

  • Lava: Fixed an issue where the DatesFromICal Lava filter did not correctly account for Daylight Saving Time when generating timestamps. This caused the UTC offset to differ between NextStartDateTime and values derived from iCalendarContent when a future date was within the Daylight Saving Time period.

  • Lava: Fixed an issue where grid lines in charts rendered using the {[ chart ]} shortcode were not visible when viewed in Dark Mode.

  • Group: Fixed an issue where individuals could not join a Sign-up Group if they matched both the "Meets" and "Warning" Criteria Data Views of a group requirement. Individuals who meet the "Meets" criteria are now allowed to join even if they also match the "Warning" criteria.

  • Communication: Fixed an issue where the Communication Entry block did not populate the From Name and From Address when launching a message from the Group Toolbox on an external site, preventing the message from being sent.

  • Event: Fixed an issue in the Registration Entry block where individuals could be charged and added to a wait list if the registration became full during submission, even when the wait list was disabled. Also corrected the message that incorrectly stated no payment was processed.

  • Workflow: Fixed issue in Obsidian Workflow Entry block that prevented values passed by query string from being set in the Workflow if they were used on the first entry form.

  • Core: Fixed an issue where external applications using Rock as an OIDC provider could not complete the login process if the individual declined authorization, due to a missing state parameter.

  • Communication: Fixed an issue where communication approvers were always redirected to the Communication Wizard page, even when the communication was originally created using the Simple Communication page. Approvers are now redirected to the appropriate editing page based on how the communication was initially created.

  • Event: Fixed a viewstate exception that occurred when disabling web caching on the Event Detail page using the admin toolbar. This could happen when a Lava template used the AddMetaTagToHead filter and interactive controls (like the web cache toggle) triggered a postback.

  • Finance: Added a new setting on the Scheduled Transaction Edit block to control how campus-specific child accounts are selected when editing scheduled gifts. Previously, this logic was always applied; it can now be configured using the "Use Account Campus Mapping Logic" setting.

  • Event: Fixed an issue in the Obsidian Registration Entry block where required fees could be bypassed during registration. The block now properly enforces required fee selection both during the registration process and at final submission.

  • CRM: Fixed an issue with Person Merge block where nameless persons would disappear after adding or removing a person from the merge request.

  • Event: Fixed an issue where individuals moved from the wait list in a Registration Instance could complete registration without completing required fields or paying required fees. The process now enforces all required steps before confirming the registration.

  • Event: Fixed an issue where submitting a registration would disable an individual's SMS setting when the "Show SMS Opt-In" option on the Registration Template was set to False. The registration process will now preserve the individual's existing SMS value unless the "Show SMS Opt-In" option is set to True, in which case the individual's opt-in preference is updated based on their response.

  • Communication: Fixed an issue with the Communication Entry Wizard block where changing the Communication Type (e.g., from Recipient Preference to Email or SMS) while creating a message could result in some recipients being excluded from the send list. This happened after advancing through the wizard and then returning to the first step to change the type before sending.

  • Reporting: Fixed an issue in the Obsidian Dynamic Data block that caused incorrect Person IDs to be passed to a Workflow when using the Launch Workflow action.

  • Core: Fixed an issue where Obsidian Grid light mode disabled pagination but still limited the grid to 50 rows, preventing additional attributes from being viewed or edited.