1.0-beta4

The forth beta release of Open Atrium. The release includes a large number of enhancements and changes for both end users and developers.

Project Structure

Open Atrium has moved from its single monolitic repository to an install profile and a drush make based build system. This is a change that primarily effects developers. The complete, ready to install, download will continue to be offered at http://openatrium.com

Developers, or other users, who wish to build Open Atrium themselves will need to have drush and drush make installed. To emulate how drupal.org builds profiles into full Drupal installs you need to use a stub makefile;

core="6.x"
projects[] = "drupal"
projects[openatrium][type] = "profile"
projects[openatrium][download][type] = "cvs"
projects[openatrium][download][module] = "contributions/profiles/openatrium"
projects[openatrium][download][revision] = "DRUPAL-6--1-0-BETA4"

Paste this code into a file called atrium_stub.make and run drush make atrium_stub.make openatrium. This will assemble a full Open Atrium build into the directory openatrium.

Upgrades

If you are upgrading existing installations of Open Atrium there are some extra steps you'll need to take for this upgrade. Before you begin a few words of caution

  • Please backup your code base
  • Please backup your database!
  • Start from a fresh Beta 4 codebase at the desired location and add your files folder or any extra modules you have added to your previous site. Do not move any of the previous Atrium modules to your new codebase.
  • Do NOT visit the site before the upgrade is complete.
  • We highly recommend using drush for this upgrade.

To upgrade your site you will need to put the Open Atrium code in to the appropriate location. Move the files directory from the old site to the new. Setup the database connection credentials. Then follow our detailed upgrade instructions.

Important note for Aegir users

Update: The step below is not necessary if you are using Aegir 0.4 alpha5

Aegir users will need to upgrade their Aegir instance to the very latest release.

You will need to symlink the new install profile to the old one if you cannot manually change the install profile namespace on your sites. Your symlinks should look like this:

profiles/openatrium/openatrium.profile -> profiles/atrium_installer/atrium_installer.profile
profiles/openatrium/modules -> profiles/atrium_installer/modules
profiles/openatrium/themes -> profiles/atrium_installer/themes
profiles/openatrium/translations -> profiles/atrium_installer/translations

Mail2web is now Mailcomment

If you were using Mail2Web on your Open Atrium site, after you upgrade to Beta 4 you will need to do the following:

  1. Go to admin/build/modules and enable the Mail Comment module.
  2. If you were using Mail2Web Extras, also enable the Mail Comment Extras module.
  3. Go to the Mail Comment settings page (admin/messaging/mailcomment) and verify that your settings are correct. Your previous settings should have been preserved. However, you will also notice a few new options, like the ability to use catchall email addresses and the option to use improved subject handling for better message threading support in email clients. Configure these options as desired.
  4. Go to the Mailhandler mailbox you had configured for Mail2Web (find it on admin/content/mailhandler) and edit its settings. At the bottom of the settings form under "Message authentication method" change this to "MailComment Default" and save the page.

MySQL version compatibility

Some versions of MySQL before 5.0.41 are know to be incompatible with the "Recent Activity" listings in Open Atrium. Upgrading to 5.0.41 or later fixes the issue.

Changelog

Modules

  • Spaces has been upgraded to 3.x series
  • Context has been upgraded to the 3.x series
  • Strong Arm has been upgraded to the 2.x series
  • ctools tools has been added.
  • Boxes has been added.
  • FeedAPI has been removed
  • Feeds has been added
  • jquery_ui has been added

Several of these modules, specifically Context and Spaces, have seen substantial improvements that are detailed in the documentation of those modules.

Fixes and Improvements

  • Renamed install profile.
  • Removed privacy per feature.
  • Removed lock preset attributes.
  • Reworked and improved dashboards.
  • Updated theme.
  • Added and updated tests.
  • Added drag and drop menu re-odering.
  • Added drag and drop block manipulation (via context module).
  • Dashboards now feature multiple layouts (via context module).
  • The User space has been reworked.
  • Gave comments click-able anchors
  • Comment preview has been fixed.
  • Using ajax pagers in many blocks.
  • ...and much more.