Thanks to UAS’s Shane Hill’s impressive recent CiviMail improvements (currently, among others, an order of magnitute speed-up in email generation…) and the forthcoming changes for DA, we decided to make a separate CiviCRM release consisting of CiviCRM 1.8 and the improved CiviMail. The release will be called CiviCRM 1.9 and is developed on the
v1.9 branch in our Subversion repository.
The new de-dupe functionality, introduced in CiviCRM 1.8, is configurable under Administer CiviCRM → Duplicate Contact Rules. This post describes the meaning of the fields and the way their contents impact the de-dupe search engine.
The first decision to make after going to Administer CiviCRM → Duplicate Contact Rules is which rule to edit. For CiviCRM 1.8 we decided to allow one rule per every contact type (individual, organization and household); in future versions this can be extended to arbitrary list of rules.
One of the main features of CiviCRM 1.8 is the ability to find duplicate contacts and merge them. The relevant spec of phase one is on our wiki, and in this post I’d like to quickly describe the merge screen. As with most of CiviCRM features, we decided to introduce merging functionality incrementally, so we can get the basic merge screen as soon as possible and then add more features based on the feedback we get.
CiviCRM is localised into several languages and used by non-English communities around the world. Before it could be localised, though, it had to be internationalised – i.e., it had to be modified to make the localisation possible. My first assignment when working on CiviCRM was to take the English-only application, internationalise it and localise it to Polish.
CiviCRM is localised into several languages and used by people all around the world. All of the CiviCRM translations are provided by volunteers; this blog post explains how to participate in the community of translators and make CiviCRM usable for people who prefer to use software in their language.