Open Atrium

1.0-beta8

Atrium 1.0-beta8 introduces several major changes:

Important

If you are using any custom features or have significant overrides to your Atrium install please read "Kit Compliance and Impact on Overridden Components" below before attempting to ugprade

Upgrading between any versions from Atrium 1.0-beta4 to 1.0-beta8

note: If upgrading a version older than beta 4, update to beta 4 first

  1. Follow the upgrade instructions here:

    https://community.openatrium.com/documentation-en/node/1942

  2. Revert all your features using drush -y fr-all from the commandline or or using the UI at /admin/build/features. Very important if you overrode any views, contexts, variable, permissions, and other configuration, on your site. This will delete your overrides and set everything back to the default Open Atrium configuration as defined in code.

    If you've made extensive overrides you will want to carefully manage this step and preserve or recreate configuration overrides.

  3. Clear your caches using drush cc all from the commandline or using the 'Clear cached data' button on /admin/settings/performance. If you clear the cache from /admin/settings/performance do not be alarmed if your theme is not working initially; it should work correctly only after you've cleared the cache (related issue for reference only http://drupal.org/node/545452).

Kit Compliance and Impact on Overridden Components

The Beta 8 release of Open Atrium includes changes to make Atrium's features Kit compliant. These changes include modifications to component machine names, such as the names of views, contexts, presets and other components provided by Atrium. If you've overridden any components in the database on your Atrium site then these overridden components will get updated by update scripts for any affected feature. For example, the views named atrium_blog and atrium_blog_comments provided by the Atrium Blog feature have been renamed to blog_listing and blog_comments respectively. If you've overridden the spaces_feature_blog context which included the atrium_blog view as a context condition and the views-atrium_blog_comments-block_1 block as a context reaction, the old view and block names which are stored in the database will get renamed to use the new names for these components. A list of the cases where renaming via the update scripts occurs or where it is not provided and must be handled manually follows.

What's handled by the Kit update scripts

Overridden contexts

The following will be handled in overridden contexts:

  • Views names used in context conditions will be renamed.
  • Block names used in context reactions, whether provided by hook_block or by a Views view will be renamed.
  • The name of the overridden context itself will be renamed.

Overridden spaces dashboards

  • Block names for blocks provided by hook_block or by Views views stored in the overridden dashboard definitions will be renamed.

Overridden spaces presets

  • Block names for blocks provided by hook_block or by Views views stored in the overridden preset definitions will be renamed.

Spaces presets names

  • Names of spaces presets themselves stored as overridden spaces presets will be renamed. For example, atrium_og_private is now known as atrium_groups_private and will be renamed where referred to in the spaces_presets table.

What's not handled by the kit update scripts

Overridden views

If a view is overridden and it, or a display it provides such as a block display, is defined in an overridden context, spaces dashboard, or spaces preset, that view's name will not get updated in the respective overridden component, nor will the overridden view itself be altered. For example, if you overrode the atrium_blog_comments view to show the 10 most recent comments instead of the 5 most recent comments, and then you overrode the spaces_dashboard_blog context in any way, the references to atrium_blog_comments in the overridden spaces_dashboard_blog context will not get renamed.

There's also a good chance overridden views will break when upgrading to beta 8. If any of your overridden views break (signs of this could be a page not working, or blocks not working) you'll either need to investigate why the view is broken (hard solution) or, delete the overridden view and override it again (the name will have changed but is likely similar, like atrium_blog view is now blog_listing) after upgrading. If you delete the overridden view after upgrading you will also need to update any context condition or reaction that uses that view and manually set it to use the new (original/default) view.

Open Atrium 1.0 Beta 8 "Seatbelts" Its a safe bet unless you're a complete dumb dumb you're not going to be hoofing it on foot in the event of a zombie outbreak. So when travelling on four wheels wear your seat belt. Nothing worse then finding yourself ejected out of your car into the loving and oh so hungry arms of zombies.

Releases