Explore projects

Adds a new field to CiviMail mailings, which allows you to set the preview text.

Provides a user interface to edit country-specific postal mailing formats.

Displays the contribution progress bar widget on contribution pages

Provides a tab on the Contact record screen that lists (nearly) all CiviMail events to do with that contact, in chronological order. This may be useful for troubleshooting, or to see which links a particular person clicked. It also includes the dates any of their emails were put on hold or released.

A CiviCRM extension to help you manage different funding pipelines, e.g. grant applications, partnerships, consultancy, that builds on CiviCase.

For CiviCRM Spark user requests and support. Please do not post private information, since this project space is public.

Synchronisation with Shine.best

Project used to document/define changes to the process of collecting stats and actionable data for CiviCRM.

Extension that provides special links that can trigger admin-defined actions before redirecting the browser to either a success or denied URL. e.g. you could record downloads of a PDF file.

Create SQL to replace the contents of your database with gibberish! e.g. developers might use this as part of a strategy to anonymise or at least obscure data for testing, training and development purposes.

A DX extension providing a fluent interface and lots of common helpers to simplify code written for custom imports.

Project space for discussing and managing virtual Civi events

Allows to crop and scale image fields in CiviCRM.

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

Onscreen tutorials for learning to use CiviCRM

Embed payment/donation forms on your external website. See README for limitations. See the Inlay extension for details on what that is.

Allows Admins to set up a 'main/parent' event with some 'related/child' events, such that registering for the 'main/parent' event also registers the participant to all the 'related/child' events.

Set up involves specifying the Event ID of the 'main/parent' event in the custom field on the 'related/child' events.

Such registrations can then be overridden if necessary by admin, eg if a user signs up for an event series E1, E2, E3 etc, but are then unable to attend E3, they can be instead registered for F3 for example