coopsymbiotic

Lets users enter a duration in hours, not just in minutes.

Makes it possible to create CiviCRM activities using a profile.

Makes it possible to set a default activity status for new activities.

Import interface for more complex, programmatic imports (can be extended by other extensions).

Re-enables the basic "Change Log" from CiviCRM after the full logging has been enabled, so that admins can see the list of changes that were done before logging was enabled.

Scheduled Job that routinely looks for duplicates (and merges them if there are no conflicts).

When is your contact usually available?

Provides a lighter workflow for the CiviCRM Event Cart. Designed for a ticket box office (ex: where you do not need the names of participants).

Sends all Drupal emails through CiviCRM. Useful to avoid configuring the SMTP services twice, and also to keep a log of password resets and other Drupal emails (they get recorded as activities on the contact record).

Sends all Drupal9 emails through CiviCRM. Useful to avoid configuring the SMTP services twice, and also to keep a log of password resets and other emails (they get recorded as activities on the contact record).

Displays the contribution progress bar widget on contribution pages

Data Explorer aims to provide an easy to use interface that can generate custom visualizations of CiviCRM data. The visualizations can then be added to the CiviCRM Dashboard, shared to external people without access to CiviCRM (using a secret key), or (eventually) as an HTML snippet that can be embedded in website content.

Enable CiviDiscounts on contributions/payment pages.

Extra Drupal8 Twig filters to workaround some Views limitations.

Attaches ICS files to event confirmation emails.

Allows event admins to redirect an Event Info page to an external URL.

Provides a way to bundle events together (at a discounted price) in the CiviCRM Event Cart (and the Boxoffice extension).

Adds support to export search results and report results directly into the Excel xlsx format.

Ever had a custom field whose possible values depended on the values of another field?