Extensions Directory
Extensions are installable packages which give CiviCRM new functionality, and this directory provides a centralized list of extensions which the CiviCRM community has created. This listing displays CiviCRM extensions that work on all Content Management Systems (CMS).
The newest extensions · Create an extension · Add an extension to this directory
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.
Processes AWS SES bounces and complaint notifications in CiviCRM. Uses native AWS bounce and complaint types instead of trying to match them to out of the box CiviCRM bounce types.
The Entity Construction Kit (ECK) provides a user interface and an API for creating and managing custom CiviCRM entities.
Transforms a checkbox custom field into a grid for selecting availabilities in the week.
This extension 'fixes' some configuration options that may have been set in English during the initial installation before you decided to switch to another language (or before improving/updating the translation files).
Converts the activity 'duration' field so that users can enter time in hours, instead of minutes.
This extension provides a generic way creating a message queue. This message queue could then be used
by other systems to retrieve changes from CiviCRM.
For example we can have a change message queue for submitting changes to an Outlook 365 address book. Every time a name of
a contact or its e-mail address is changed. A message is added to queue. Outlook 365 can then read message by message to process the
changes.
For developers it good to know that the queue used could be extended so that for example you can push the messages to RabbitMQ.
(RabbitMQ is an implementation of a message queue).
By default this extension comes with a CiviCRM Database Queue. This queue could be read with the API ChangeMessageQueue.get
by other systems to retrieve changes from CiviCRM.
For example we can have a change message queue for submitting changes to an Outlook 365 address book. Every time a name of
a contact or its e-mail address is changed. A message is added to queue. Outlook 365 can then read message by message to process the
changes.
For developers it good to know that the queue used could be extended so that for example you can push the messages to RabbitMQ.
(RabbitMQ is an implementation of a message queue).
By default this extension comes with a CiviCRM Database Queue. This queue could be read with the API ChangeMessageQueue.get
Define conditional rules of allowed field values based on the value selected in another field.
Blocks a configurable list of message templates emails (such as contribution receipts) and optionally records them as an activity.
Adds new settings to determine if a priceset field value should be displayed for one-time donations, recurring or both.
