I have been asked to webmaster a web site that is built upon Open Atrium (http://openatrium.com/). Open Atrium is a team collaboration framework built upon a Drupal core plus their special "hot sauce" collection of modules. I have read some discussion suggested it has its own update mechanisms.
Somebody set up the site on a server and handed it over to me. I have limited experience with Drupal. I have created a couple sites using Drupal, but have not had the time to devote to get to the top of that reputed "steep learning curve". I have attended several local meetings with my collaborator, Bob McFarland.
I got a user group to kick the tires a bit on the site and one of the first discoveries is that we cannot upload photos. I thought it may be due to the fact that my Drupal 6 core was out of date. I successfully updated a single module that was reported out of date, but I was a bit nervous about updating the entire Drupal core because I didn't know how it might affect the Open Atrium modules. I have been sitting on it for two months due to higher priority work. I now have two weeks with some bit of time and I would like to fix the site and move on to the next comment which was something about importing iCal calendars.
Krista suggested that my problem may be due to permissions on my directories. This is an excellent suggestion which I will check out.
Does anybody out there have specific experience with Open Atrium? Or can otherwise put my mind at ease about how to update from Drupal 6.19 to Drupal 6.20 without destroying the other modules?
Comments
tar the folder where drupal
tar the folder where drupal is install and backup your db before doing anything.
Usually, I create a mirror site on a test machine and do the upgrade there, figure out the issues and than do the update to the real site.
Anyway: backup is the answer!!!!
I use OA
You shouldnt have any trouble with the upgrade from 6.19 to 6.20, assuming everything is up to date. My OA install is on 6.20 and works fine. That said, for any upgrade of any production site, you should ALWAYS make a copy on dev, try it, and if everything looks good deploy the changes.
I would guess -- in agreement with Krista -- that the photos issue is not related to your Drupal version, but to either filesystem settings (check to make sure there's a valid temp path in admin/settings/file-system, and that both that and the regular files dir are writable).
Best Backup Plan?
What do you think of downloading all the files from the production server to my MacBook using MAMP? I guess the database needs to be exported and imported. If I can get the present site to work on my MacBook, I guess I should feel confident. Somehow I feel that making that backup won't be totally trivial, but it should be a good exercise. What is the best help file I can follow to make the backup?
If you Are familiar with
If you Are familiar with commando line, this is the commando that you would use:
- mysqldump -u (user) -p (database) > (filename)
You will be asked the password for the user you spedify.
If you Are familiar with
If you Are familiar with commando line, this is the commando that you would use:
- mysqldump -u (user) -p (database) > (filename)
You will be asked the password for the user you spedify.
if not...
You can try http://drupal.org/project/backup_migrate. You'll have to install drupal and the bam module to restore from the backup. So dl all the site code, create a db, run install.php, then enable bam and restore from the file.