Permalink
Browse files

Streamline upgrade instructions.

  • Loading branch information...
1 parent 4474e33 commit bedfd82a2154bdb1d519e3305d88dc974349442c yhahn committed Aug 24, 2010
Showing with 12 additions and 23 deletions.
  1. +12 −23 UPGRADE.txt
View
@@ -1,41 +1,30 @@
-# $Id: UPGRADE.txt,v 1.6 2010/08/24 05:48:22 yhahn Exp $
+# $Id: UPGRADE.txt,v 1.7 2010/08/24 05:58:21 yhahn Exp $
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. Backup both the code and database of your old Atrium site.
-
-2. Replace your Atrium codebase by moving your old Atrium drupal directory out
- of the way and replacing it with the new Atrium directory (this ensures that
- any files that have been moved or deleted are properly cleaned up). Be sure
- to preserve the files directory of your site (usually `sites/[x]/files`)
- and any site-specific modules, themes and settings.
-
-3. Clear your caches using `drush cc all` or clicking the `Clear cached data`
- button on the `admin/settings/performance` page.
-
-4. Run any database updates using `drush updb` or `update.php`.
-
-5. For more detail on steps 1-4 above see
+1. Follow the upgrade instructions here:
https://community.openatrium.com/documentation-en/node/1942
**The following steps are specific to Atrium 1.0-beta8**
-6. Run `drush -y fr-all` to revert all of your 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 the code.
+2. Run `drush -y fr-all` to revert all of your 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 the
+ code.
If you've made extensive overrides you will want to carefully manage this
step and preserve or recreate configuration overrides.
-7. The last required step is to clear your caches again (see step 3). If you
- clear the cache from `admin/settings/performance` do not be alarmed if your
- theme is not working correctly; it should work correctly after you've
- cleared the cache (issue for reference only http://drupal.org/node/545452).
+3. Clear your caches using with `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).
Upgrading from Atrium 1.0-beta3.x to 1.0-beta4

0 comments on commit bedfd82

Please sign in to comment.