CiviCRM 3.2.5: security release

Published
2010-11-18 01:25
Written by
shot - member of the CiviCRM community - view blog guidelines

CiviCRM 3.2.5 is a security release, fixing security vulnerabilities in CiviCRM Ajax and REST interfaces and export code. We strongly recommend that you upgrade your CiviCRM installation to 3.2.5.

We just released CiviCRM 3.2.5 – it is now available for download. You can also try it out on our demo site. This release introduces quite a few bug fixes; for full list of things that has been fixed/improved in 3.2.5, please take a look at our issue tracker.

For more details on major new features/highlights, please refer to 3.2 release blog post, here's the short list:

  • Usability improvements
  • Support for PHP 5.3
  • CiviCase Phase 3
  • CiviEvent workflow improvements
  • Free-tagging, and Tags for Cases and Activities
  • No standalone version

 

Downloads

You can download the release from SourceForge – select from the civicrm-stable section. The filenames include the 3.2.5 label: civicrm-3.2.5. Make sure you’re downloading correct version: for Drupal or Joomla.

New Installations

If you are installing CiviCRM 3.2.5 from scratch, refer to the installation guide:

 

Upgrading 2.2.* or 3.0.* or 3.1.* Sites to 3.2

The procedure for upgrading to 3.2.5 is the same as for upgrading to 3.0.x. You can upgrade directly from 2.2.x or 3.0.x or 3.1.x. Instructions:

  • Drupal
  • Joomla
  • We will continue to include automated upgrades for subsequent releases of 3.2 - so you should be able to upgrade your site easily over the course of the release cycle.
Filed under

Comments

Anonymous (not verified)
2010-11-22 - 02:43

"We will continue to include automated upgrades for subsequent releases of 3.2 - so you should be able to upgrade your site easily over the course of the release cycle."

I'm running 3.2.3. "automatic" sounds nice. How do I get that automated process happening? I found a 16-step very non-automatic-looking process detailed on the wiki.

 

Advice much appreciated,

 

Rich

For a production site you probably don't want automatic. The instructions are a thorough list for a live site. On a test site it's just download, unpack, and run the upgrade script. I think automatic refers to the upgrade script.