The CiviCRM core team and community of developers and implementers are proud to present...
Which one should I use?
In most situations, and if you are new to CiviCRM, you should choose the latest stable version. It contains new features and receives the most support. 4.2 LTS (long term support) is provided for those organizations who are using an older version of CiviCRM and are not yet ready to upgrade; it receives critical bug fixes only. More about 4.2 LTS.
Noteworthy Fixes in 4.3.6:
- Can't select individual contacts on the Search Results page
- Automated recurring contribution "civicrm_line_item" records have wrong financial type id
- Logging Broken for Financial Records Following Upgrade
- Survey data entry form not reliably showing contact fields before question fields
» View the full list of improvements for 4.3.6
CiviCRM is free, open source software made possible through contributions from people like you. If your organization benefits from using CiviCRM AND from the great new features in this release, please consider making a recurring contribution to support the project.
Compatibility
CiviCRM is more compatible than ever, version 4.3 has been tested to run with:
- Drupal 7
- Drupal 6 (community supported)
- Joomla 2.5
- Wordpress 3.4 and higher
New Installations
If you are installing CiviCRM 4.3 from scratch, please use the corresponding automated installer instructions:
Upgrading to 4.3
If your site is highly customized with special code or theming for CiviCRM you will want to upgrade a test copy first and test your customizations. For everyone else, follow these simple steps to get yourself up and running with 4.3.
Contributors
Community support and engagement is the force that sustains and drives CiviCRM forward. This release would not have been possible without the incredible contributions of these people and organizations:
AGH Strategies - Andrew Hunt; Backoffice Thinking; Chris Burgess; Circle Interactive - Andrew Walker, Dave Moreton; CiviDesk - Nicolas Ganivet; CiviHosting - Hershel Robinson; Community Builders; Compucorp; Confluence - Frank Gomez; Dave D; EE-atWork - Erik Hommel; Electronic Frontier Foundation - Micah Lee, Kellie Brownell; Emphanos - Allen Shaw; Fuzion NZ - Eileen McNaughton, Peter Davis, Torrance Hodgeson; Jim Meehan; JMA Consulting - Joe Murray; Keith Morgan; Ken West; Korlon - Stuart Gaston; Koumbit - Samuel Vanhove; Lighthouse Consulting and Design - Brian Shaughnessy; Mathieu Lutfy; New York State Senate - Ken Zalewski; NfP Services (MTL Software Group) - Jag Kandasamy, Rajesh Sundararajan; Niro Solutions; Noah Miller; Palante Technology Cooperative - Jon Goldberg; Progressive Tech Project - Alice Aguilar, Jamie McClelland; Paul Delbar; Registered Nurses Association of Ontario; San Francisco Baykeeper - Eliet Henderson; Tech to the People - Xavier Dutoit; Third Sector Design; Veda Consulting - Parvez Saleh; Web Access - Pradeep Nayak; Zing - Simon West, Andrew Tombs.
Comments
Note that we don't see it as important for you to upgrade to 4.2.11 if you are already on 4.2.10 (although you may choose to).
The 4.2.11 release contains a fix related to http://issues.civicrm.org/jira/browse/CRM-11331 which could require you to update any custom custom searches you have (ie. ones that were not shipped with core)