| | 1 | =================================== |
| | 2 | Migrating to eduCommons 3.1.1 |
| | 3 | =================================== |
| | 4 | |
| | 5 | |
| | 6 | Preparation |
| | 7 | ----------- |
| | 8 | A few things you should do before beginning the migration: |
| | 9 | |
| | 10 | 1. VERY IMPORTANT: SAVE A BACKUP OF YOUR Data.fs FILE, which is located in the [old instance home]/var directory of your eduCommons site. This file contains all of the content for your site. (This way you will able to restore your file from this Data.fs file if anything goes wrong.) |
| | 11 | |
| | 12 | 2. Using the Zope Management Interface (ZMI), export any customizations you have made in your [old site] --> portal_skins --> custom folder and then delete all files in the custom folder. You can re-import these customizations once you have migrated the site. |
| | 13 | |
| | 14 | 3. Verify that your current instance is eduCommons-3.0.2-final. |
| | 15 | |
| | 16 | |
| | 17 | Migration of eduCommons 3.0.2-final to 3.1.1 |
| | 18 | -------------------------------------------------- |
| | 19 | |
| | 20 | The migration eduCommons from version 3.0.2-final to version 3.1.1 |
| | 21 | includes the following: |
| | 22 | |
| | 23 | 1. Movement of Data.fs file to a new 3.1.1 instance |
| | 24 | |
| | 25 | 2. Migration to Plone 3.0.6 |
| | 26 | |
| | 27 | 3. Migration to the eduCommons 3.1.1 instance |
| | 28 | |
| | 29 | 4. Final steps |
| | 30 | |
| | 31 | Movement of Data.fs file to a new 3.1.1 instance |
| | 32 | ------------------------------------------------------ |
| | 33 | |
| | 34 | For the first step, you will move the Data.fs file from the old instance to |
| | 35 | the new instance. First of all, install an eduCommons-3.1.1 |
| | 36 | instance using the installations instructions found in [new instance home]/eduCommons/docs/. Stop both sites. Then |
| | 37 | copy the Data.fs file from the var directory of the old site to the |
| | 38 | var directory of the new site: |
| | 39 | :: |
| | 40 | |
| | 41 | sudo cp -rvfp [old instance home]/var/Data.fs [new instance home]/var/ |
| | 42 | |
| | 43 | |
| | 44 | Migration of Plone |
| | 45 | ------------------ |
| | 46 | The following steps need to be performed in the ZMI, as eduCommons-3.1.1 utlizes Plone 3.0.6, instead of 3.0.4: |
| | 47 | |
| | 48 | 1. Open your 3.1.1 eduCommons site in the ZMI. (click educommons setup, then click Zope Management Interface.) |
| | 49 | |
| | 50 | 2. Run portal_migration migration (click the upgrade button on the migrate tab) |
| | 51 | |
| | 52 | |
| | 53 | Installation of FileSystemStorage Product |
| | 54 | ----------------------------------------- |
| | 55 | At this point in time, we need to ensure that the FileSystemStorage AddOn Product is installed: |
| | 56 | |
| | 57 | 1. Open your 3.1.1 eduCommons site in the ZMI. (click educommons setup, then click Zope Management Interface.) |
| | 58 | |
| | 59 | 2. Navigate to portal_quickinstaller |
| | 60 | |
| | 61 | 3. Select FileSystemStorage |
| | 62 | |
| | 63 | 4. Press Install |
| | 64 | |
| | 65 | Migration of the eduCommons 3.1.1 instance |
| | 66 | ------------------------------------------------ |
| | 67 | eduCommons 3.1.1 uses the portal_setup tool to perform the necessary upgrade from 3.0.2 to 3.1.1: |
| | 68 | |
| | 69 | 1. Open your 3.1.1 eduCommons site in the ZMI. (click educommons Setup, then click Zope Management Interface.) |
| | 70 | 2. Navigate to portal_setup |
| | 71 | 3. Press the 'Upgrades' tab |
| | 72 | 4. From the drop down menu, select 'Products.eduCommons:default' and click Choose Profile button. |
| | 73 | 5. Choose the 'Migration :: 3.0.2 to 3.1.0' option |
| | 74 | 6. Press Upgrade |
| | 75 | |
| | 76 | |
| | 77 | Final Steps |
| | 78 | ----------- |
| | 79 | |
| | 80 | Your site should now be migrated. Navigate to your site in the browser and ensure it has migrated. |
| | 81 | |
| | 82 | |
