From 7220ee617829f20f8404b3feb47a30e16d756009 Mon Sep 17 00:00:00 2001 From: georgeowell Date: Tue, 3 Sep 2019 18:39:44 +0100 Subject: [PATCH] Proofed original text and added some corrections --- .../2019-08-30-civicrm-mailing-validation.md | 15 ++++----------- 1 file changed, 4 insertions(+), 11 deletions(-) diff --git a/src/_posts/2019-08-30-civicrm-mailing-validation.md b/src/_posts/2019-08-30-civicrm-mailing-validation.md index dc670a9..3f930eb 100644 --- a/src/_posts/2019-08-30-civicrm-mailing-validation.md +++ b/src/_posts/2019-08-30-civicrm-mailing-validation.md @@ -7,18 +7,11 @@ category: howto date: 2019-08-30 --- -A couple of our clients use [CiviCRM](https://civicrm.org/); one of them uses -the "Mailing" features to send out emails to their supporters. Apparently, -they're facing a bug where if someone sends out a Mailing with the same name -(not subject line, just the internal identifier 🙄) as an existing one, it'll -freeze the CRM later. +Some of our clients use [CiviCRM](https://civicrm.org/) which is a popular open source "constituent relationship management" platform; +one of those clients uses the "Mailing" features to send out emails to their supporters. We found out they're experiancing a bug where a user sends out a mailing with the same name (not subject line, just the internal identifier 🙄) as an existing mailing, it'll cause the CRM to +freeze up at a later time. -As an added challenge, the Mailings feature of CiviCRM [now uses -AngularJS](https://docs.civicrm.org/dev/en/latest/framework/angular/) following -a recent rebuild, and there aren't many tutorials or examples out there. -Luckily, the CiviCRM developer community was super-helpful, and we managed to -sort out some in-form validation to prevent duplicate Mailing -names for our client… and now for you, too! +As an added challenge, the mailings feature of CiviCRM [now use AngularJS](https://docs.civicrm.org/dev/en/latest/framework/angular/) following a recent rebuild by the developers, and there aren't many tutorials or examples out there of workarounds to this issue. Luckily, the CiviCRM developer community was super-helpful, and we managed to sort out some in-form validation to prevent duplicate mailing names for our client and now for you, too! ## Create a new extension