We are excited to announce that the first BETA release of version 3.2 is now available for download. You can also try it out on our sandbox site. Please remember this is a BETA release and it should NOT be used on production sites.
This release includes several major new features/highlights:
- Usability improvements - Better looking and more intuitive Contact Summary Page. The new "Actions" button provides 1-click access to most contact-related forms. New clean and consistent icons have been implemented to provide helpful visual cues. You can now get a configurable contact summary pop-up from search results by mousing over the contact icon on any row. We'll be blogging with more details on these usability features during the release cycle.
- Support for PHP 5.3 -This release supports PHP 5.3.
- CiviCase Phase 3 - Thanks to the Physicians Health Program folks for pushing CiviCase to the next level! You can check out the phase 3 enhancements here.
- CiviEvent workflow improvements - Streamlining the workflow for events, providing 1-click access to event related screens from the configuration panel, and generating event name badges. For more details check CRM-6230 and CRM-6294.
- Free-tagging, and Tags for Cases and Activities - You can add one or more free-tagging "taxonomies" - called Tagsets - for use with contacts, cases and / or activities. You can also specify which tags can be used for which types of records.
- Standalone version dropped - Please note that we are dropping support for the Standalone version in 3.2. We recommend that current standalone users convert their installations to run under a basic Drupal install during this release cycle.
Step up and help out!
CiviCRM 3.2 Beta 1 release is a great occasion to get involved in CiviCRM community. There are many ways you can help make this release better and bug free.- Log in to the CiviCRM 3.2 public sandbox and try out your favourite features. If you find a problem, please report it on the appropriate forum board. Remember that sandbox data is periodically reset.
- Download the tarball and upgrade a copy of your site to 3.2 - let us know if you encounter any problems. This is an especially valuable contribution since we need to have the upgrade process tested on different sets of data. After you've done this, play around with your favourite features, with your local data. Problems appearing? Use the CiviCRM 3.2 release testing board on the forums to discuss problems and find answers!
- If you're a developer and have PHP skills, we strongly encourage you to develop and attach a code patch AND a unit test along with any bug you report through our issue tracker. Ping us on IRC if you need help figuring out how to do this.
Existing issues
CiviCRM 3.2 beta 1 is not bug free, it's just the first step on the way to the stable version. We know about some problems and are working hard to fix them before the next release (expect it around Wednesday next week). The list of currently open issues is available here. If you notice any new problems, please report them as mentioned above.
Downloads
You can download the release from SourceForge - select from the civicrm-latest section. The filenames include the 3.2 Beta 1 label: civicrm-3.2.beta1. Make sure you're downloading correct version: for Drupal or Joomla.
New Installations
If you are installing CiviCRM 3.2 Beta 1 from scratch, please use the 3.0 versions of the automated installer instructions (the installation process has not changed):
Comments
Detailed comments perhaps belong on the forums but WTH will post a couple quick things here. Installed 3.2 beta 1 on a testing/dev site running Drupal 6.17. One, on CiviCRM main page the links in the Help menu lead to 3.1 pages not the 3.2 doc - also links to doc should open a new window so your logged in session in Civi is not disrupted (small thing and probably a setting I've overlooked somewhere). BTW looking at the CiviCRM optional modules section on the Drupal module admin page, there's an entry for CivCRM NYSS which I can't seem to find any info on anywhere. It lists itself as 3.1 and probably appeared when I loaded CiviEngage and I'm just noticing it, but it still needs some info available on what it does and how to use it, since it's showing up on the admin choices. My guess is it's related to the NYSS Drupal contrib modules but at some point it would be really nice to find some sort of doc in one place for the various bits and pieces - new book has a good section on CiviEngage actually. Overall, upgrade from 3.1 thru alpha and now beta of 3.2 has gone smoothly thus far.
Hi,
What's the recommended method for upgrading from 3.2.x (e.g. 3.2alpha to 3.2beta)?
Is it the same method as for upgrading from 3.1, 3.0, 2.x, etc? Or is there a patch file somewhere?
Thanks
... is the same for any upgrade (beyond 2.2.x). This includes upgrading between beta's and from the final beta to stable.
Drupal upgrades
Joomla upgrades