C

coopsymbiotic

Alters the "Email Invoice" form to add a few fields similar to other email forms (to, cc, subject with tokens, message templates), as well as generates payment links for pending contributions that can be copy-pasted from the View Contribution page.

Provides an interface to live-translate strings in Transifex, and also to export/import strings from various CiviCRM settings (contribution pages, events, etc).

Sends you a detailed email when a CiviCRM fatal error occurs.

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

Attaches ICS files to event confirmation emails.

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

Adds new settings to determine if a priceset field value should be displayed for one-time donations, recurring or both.

Changes the input type on a few fields (ex: email, phone, amount) and helps format postcodes, phone numbers.

Fixes CiviCRM configurations that were left in English if the admin installed CiviCRM in English and then switched languages.

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

Enable CiviDiscounts on contributions/payment pages.

When is your contact usually available?

Provides an alternative visual to CiviCRM radio buttons. In itself, this extension does not do anything, but other extensions can call it, such as recurringbuttons.

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.

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).

A timetracker extension for CiviCase.

Helps throttle CiviCRM forms against abuse/spam.

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

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