ChurchTools Web v3.58.0

Improvements

• People & groups
  • The process of deleting users has been improved. It had become a bit slow in the last version.
  • The internal group permission “Can create groups” now also allows users to copy groups (limited to subgroups of the group for which the permission was granted).
  • When performing a registration via the group’s website, it is now possible to sign up a spouse or children under the age of 16, even if those individuals are not yet registered in ChurchTools. Previously, family members could only be signed up if they were already registered in ChurchTools.
  • There is now a “Back” button on the group details page of the group homepage.
  • The settings for the group homepage have been updated so that you can now view them all in the same window.
• Finances
  • In the transaction list, it is now possible to freeze multiple transactions in a single step.
  • There is now a donor overview, in preparation for the donation certificate.
• Calendar
  • There is now a visual editor for creating an embedded calendar.
• Reports
  • There is a new ad hoc report on app usage.
  • The labels for an ad hoc query are now displayed in the translated language, if a translation is available.
• REST API
  • New endpoint for batch commands: PATCH /finance/transactions

Fixed errors

• General
  • In tables, the offset is now reset when the maximum number of rows displayed is changed.
  • The pagination links in the standard table have been updated and improved.
  • In the birthday list, the age is displayed only if a valid year is provided.
• People & groups
  • The “Edit Group Homepage” link in a group is now displayed if there is at least one public group in that group’s hierarchy.
  • The order of the data fields in the request email sent to the leader of a public group has been corrected.
  • It is no longer possible to create a form letter without a recipient.
  • The privacy policy now opens in a new tab in the embedded view of the group homepage.
  • Simple HTML is now displayed correctly again in the group description.
  • The “Tag-Select” feature for groups is no longer covered by the OSM copyright.
  • The default value for checkboxes is now set correctly in the groups registration form (1 = true, anything else = false)
  • When creating new records, only relevant additional fields are displayed.
  • The “title” is now also set for Selects in the group participant list, ensuring that truncated content remains readable.
  • A DB field of the Yes/No type is now rendered as such and no longer as 0 and 1.
  • The filter selections now take into account the sort keys for stations and statuses.
  • It is now possible again to delete people from the archive, even if they are still in groups.
  • The old group homepage now includes dropdown menus for gender, which are not required fields.
  • During registration for public groups, checkboxes that are not required fields now behave correctly if no selection is made.
  • The path to a public group’s URL can now optionally end with a “/”.
• Calendar
  • For the public user, all calendars are selected by default again.
  • In the settings for a calendar, you can once again delete a station and a template.
• Events
  • After refreshing the master data page, you could no longer add new roles. This issue has now been resolved.
  • Groups are now sorted alphabetically in the service selection.
  • If you decline a service request or confirmation by pressing Enter, this action is now saved and the events are updated.
  • The combined filter for “Service Group” and “My Filters” now works as an “AND” operator again.
  • If an event disappears when a filter is enabled because it no longer meets the criteria, the heading will now also disappear if it was the only element.
• Check-in
  • When a new person is added to the group, the selected group remains unchanged. A different group had been selected previously.
• Wiki
  • Scrolling to the headings now works again in all browsers.
• Finances
  • You can now also create new fiscal years in Safari.

Security fix

• General
  • Fixes unauthorized access to the Login token.
  • The LDAP service now checks whether two-factor authentication is enabled when authenticating users. If so, the user must append the generated token to their password when performing a Login to the external system. This behavior of the LDAP service can be disabled in the admin settings.