Name CAAT as the client

This commit is contained in:
c v t 2019-09-06 11:17:12 +02:00
parent d97b124a79
commit 04f2e8eb28

View File

@ -7,12 +7,16 @@ category: howto
date: 2019-08-30 date: 2019-08-30
--- ---
Some of our clients use [CiviCRM](https://civicrm.org/), a popular open source We support [Campaign Against Arms Trade](https://caat.org.uk), a right-on group
"constituent relationship management" platform. One of those clients regularly that works to end the international arms trade, with their technology –
uses the "Mailing" features to send out emails to their supporters, and told us including CiviCRM](https://civicrm.org/), a popular open source
that they're experiancing a bug: if a user sends out a mailing with the same "constituent relationship management" platform.
name (not subject line, just the internal identifier 🙄) as an existing one,
it'll cause the CRM to freeze up elsewhere. Among other things, CAAT uses CiviCRM's "Mailing" features to send out emails to
their supporters, and they told us that they're experiencing an annoying bug: if
a user sends out a mailing with the same name (not subject line, just the
internal identifier 🙄) as an existing one, it'll cause the CRM to freeze up
elsewhere.
As an added challenge, the mailing features of CiviCRM [now use As an added challenge, the mailing features of CiviCRM [now use
AngularJS](https://docs.civicrm.org/dev/en/latest/framework/angular/) following AngularJS](https://docs.civicrm.org/dev/en/latest/framework/angular/) following
@ -109,7 +113,7 @@ Activate the extension, e.g. with `cv`
$ cv en mailing $ cv en mailing
Now, open a mailing and try to give it the same name as an existing one you Now, open a mailing and try to give it the same name as an existing one – you
should see the field border turn red, and you'll be prevented from continuing or should see the field border turn red, and you'll be prevented from continuing or
sending the mailing: sending the mailing:
@ -120,3 +124,6 @@ sending the mailing:
It does seem like a red border sometimes hangs around the field label even after It does seem like a red border sometimes hangs around the field label even after
the value is valid again… but apart from that, the feature is working great! the value is valid again… but apart from that, the feature is working great!
Lastly, props to CAAT for being a great member of the CiviCRM community and
supporting us writing this post to share our work with y'all.