CiviRules release 2.0 is available

CiviRules 2.0 is now available for you all!

We (Jaap Jansma, Klaas Eikelboom and me) are about to complete a little CiviRules sprint of 2 days (funded by CiviCooP). We have fixed quite a few issues, closed some that we thought were not applicable any more, introduced a few new conditions and actions and updated the documentation. And we are about to round it off with the new release CiviRules 2.0 and moving our repository to the CiviCRM GitLab server. We expect to do this tonight or tomorrow morning.

Just added a small extension to allow many invoice addresses for a contact based on relationships

I have just published the Invoice Address API (https://civicrm.org/extensions/invoice-address-api).

The development of the extension was funded by Domus Medica vzw. They are a membership organization specifically for GP's (general practitioner) in Flanders and Brussels.

Using CiviRules for a Petition Journey at Amnesty International Vlaanderen

At Amnesty International Vlaanderen we are starting a Petition Journey. The aim is to improve the engagement of people that sign a petition for the first time as their first point of contact with Amnesty. We then would like to send them an email with a survey immediately, and then for 5 weeks an email each week. One will be informing with a video link, one will be an invitation to register for an event in the same campaign, one will be to invite them to sign another petition etc.

Tiny extension to prevent REST API request being processed when your site is in maintenance mode.

I just published a small extension (funded by Amnesty International Vlaanderen) to prevent the REST API requests still coming through when the site is in maintenance mode.

The extension is CiviCRM native and the structure is based on the CiviCRM User Framework. However, as I have little to no experience with a CMS other than Drupal, I have only implemented the Drupal module. Would be really great if others could add the same trick for the other CMS's!

Logic: