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
Embed payment/donation forms on your external website. See README for limitations. See the Inlay extension for details on what that is.
Allows you to specify administrators who have access to groups and contacts within those groups.
Contacts will only be able to see groups for which they are administrators and the contacts in those groups.
Contacts will only be able to see groups for which they are administrators and the contacts in those groups.
Purge Logs is a configurable API Job, to remove files older than a defined timeframe.
Adds a button to cancel/transfer an event from the user dashboard.
A CiviCRM extension to automatically add information about your contacts' electoral districts.
Experimental extension that makes it possible to create new activities using a profile, when used in combination with the remoteform extension.
Adds a user interface for adding custom fields to soft credits. Also adds searching by soft creditee name.
Lookup the value of a given field based on the value of another field. For example, based on the postcode of a contact, on a contribution page or on an administrative page, you may want to lookup the region, district, state/province, or can be used to determine a medical clinic, closest office, etc.
Provides CiviCRM support for the Canada Post "Address Complete" service.
Makes it possible to re-order the dashboard elements (including those defined by extensions).
This is a CiviCRM extension that enables a single Contribution page to have options for multiple recurring Contributions, each with different recurring payment schedules (frequency). Such that you can provide donation frequency options or membership renewal of daily, weekly, monthly or yearly with varying intervals. This is implemented by adding two new fields to each Priceset Option within a Priceset:
1. Recurring Contribution Unit: Which determines if this option should generate a recurring Contribution. Options: no recurrence, day, week, month, year
2. Recurring Contribution Interval: Which determines the interval of the recurrence. Integer field.
When the Contribution page is processed, each Priceset Option with a defined Recurring Contribution Unit will result in the creation of a recurring Contribution according to the options selected.
1. Recurring Contribution Unit: Which determines if this option should generate a recurring Contribution. Options: no recurrence, day, week, month, year
2. Recurring Contribution Interval: Which determines the interval of the recurrence. Integer field.
When the Contribution page is processed, each Priceset Option with a defined Recurring Contribution Unit will result in the creation of a recurring Contribution according to the options selected.
This extension fixes a core flawless.
When you merge two contacts and a case is moved from one to the other then the case is copied and the old one
is marked as deleted.
Sometimes you want to keep the case (for example if you want stick with the case id).
When you merge two contacts and a case is moved from one to the other then the case is copied and the old one
is marked as deleted.
Sometimes you want to keep the case (for example if you want stick with the case id).
This extension exposes table name/column name/machine name fields to the custom data UI.
