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
Permet d'utiliser la passerelle de paiement d'HelloAsso. Avec le retour de notification d'HelloAsso.
Extends the functionality of the domain + multisite extension to include additional implicit filtering per site and tools to manage menus across multiple sites. Designed to support a case with a central site with a collection of subsites.
Provides a way to record associations between contacts and arbitrary other entities, similar how CiviCRM "relationships" record associations between contacts and other contacts.
Extension to add support for embedding CiviCRM Personal Campaign Page Create page functionality using shortcodes in Wordpress
This extension allows an administrator to link a 'parent' civievent and a 'child' civievent. This pairing allows for an implementation of
"group" registration, by separating a payment in the 'parent' event for a group of participants, from the individual participants' registration process
in the 'child' event.
"group" registration, by separating a payment in the 'parent' event for a group of participants, from the individual participants' registration process
in the 'child' event.
This extension provides a set of Actions for CiviRules. These Actions enable integration to a process engine capable of executing long running business processes. Process "flows" may orchestrate both the internal CiviCRM APIs and also external APIs to loosely coupled systems.
The initial Alpha release will provide REST Actions to a Python container within the same docker environment (for security reasons). A fully functional Docker image for each CMS will be available for download from the repo, to make evaluation as simple as possible. For production environments, additional steps will be required to ensure security. You are strongly advised to seek help from a CiviCRM partner or cyber security expert before running this in a live environment.
Eventually we plan to provide some example Python flows, admin forms to view audit trails and manage Running, Completed, Faulted and Archived process instances.
For more help, ping us an email: support@encircle.co.uk.
The initial Alpha release will provide REST Actions to a Python container within the same docker environment (for security reasons). A fully functional Docker image for each CMS will be available for download from the repo, to make evaluation as simple as possible. For production environments, additional steps will be required to ensure security. You are strongly advised to seek help from a CiviCRM partner or cyber security expert before running this in a live environment.
Eventually we plan to provide some example Python flows, admin forms to view audit trails and manage Running, Completed, Faulted and Archived process instances.
For more help, ping us an email: support@encircle.co.uk.
The sole purpose of this CiviCRM extension is to adjust a contribution activity's date if the receive date of the contribution has changed.
See also: https://issues.civicrm.org/jira/browse/CRM-17961
See also: https://issues.civicrm.org/jira/browse/CRM-17961
Provides a way to bulk-update recurring contribution records, e.g. if your membership prices go up.
Allows administrators to change an event's "creator". This is helpful if you use the "creator" field to control access to contacts with [View My Event Participants](https://civicrm.org/extensions/view-my-event-participants). You can also use it to create Views or SearchKit displays of a person's events.
