Changeset 52378
- Timestamp:
- 01/07/08 15:53:27 (2 years ago)
- Files:
Legend:
- Unmodified
- Added
- Removed
- Modified
- Copied
- Moved
CPS3/products/CPSDefault/trunk/doc/howto-upgrading_to_cps3.4.txt
r52296 r52378 3 3 ==================== 4 4 5 :Author: Lennart Regebro 5 :Authors: - Lennart Regebro 6 - Marc-Aurèle Darche 6 7 7 8 :Revision: $Id$ … … 11 12 12 13 13 CPS 3.4.0 supports upgrading from CPS 3.3.8. 14 CPS 3.4.0 supports upgrading from CPS 3.3.8. 14 15 15 16 CPS 3.4.2 supports upgrades from CPS 3.2.4 and 3.3.* (and of course from CPS 3.4.0). … … 18 19 19 20 The best way to upgrade is to first do a new install of CPS 3.4 in a new 20 directory, and make sure it runs. Remember to make sure that you have all 21 products that you have on your old site installed in the new site, or the upgrade will not work. Some products that exists in CPS 3.2 and 3.3 have been deprecated in 3.4. These exist in the 3.4 legacy package: 21 directory, and make sure it runs. Remember to make sure that you have all 22 products that you have on your old site installed in the new site, or the 23 upgrade will not work. Some products that exists in CPS 3.2 and 3.3 have been 24 deprecated in 3.4. These exist in the 3.4 legacy package: 22 25 23 26 http://www.cps-project.org/static/src/CPS-legacy-3.4.2-1.tar.gz 24 27 25 If you have any custom products, you will need to install them as well, and make any necessary changes to the for compatibility with CPS 3.4. See http://svn.nuxeo.org/trac/pub/file/CPS3/trunk/doc/whats-new-cps-3.4/whats-new-cps-3.4.txt 28 If you have any custom products, you will need to install them as well, and make 29 any necessary changes to the for compatibility with CPS 3.4. See 30 http://svn.nuxeo.org/trac/pub/file/CPS3/trunk/doc/whats-new-cps-3.4/whats-new-cps-3.4.txt 26 31 for more information about things that have changed on the technical level. 27 32 28 After you have CPS 3.4 running, you stop the new server and delete the 29 database in the new installation, and copy in the database from the production site. (You don't have to stop the production site, but of course, any changes made to the production site after you copied that database will be lost from the upgrade). 33 After you have CPS 3.4 running, you stop the new server and delete the database 34 in the new installation, and copy in the database from the production site. (You 35 don't have to stop the production site, but of course, any changes made to the 36 production site after you copied that database will be lost from the upgrade). 30 37 31 38 In Unix:: … … 37 44 38 45 39 The procedure from here on varies sligthly depending on what version of CPS you are upgrading from. 46 The procedure from here on varies slightly depending on what version of CPS you 47 are upgrading from. 40 48 41 49 … … 54 62 be no upgrades listed. 55 63 64 56 65 Upgrading from CPS 3.3.8 or 3.2.4 57 66 ================================= 58 67 59 1. Go to the CPS site and in the ZMI add a `CPS Setup Tool` from the `CPS Tools` 68 1. Adding `portal_setup` 69 70 Go to the CPS site and in the ZMI add a `CPS Setup Tool` from the `CPS Tools` 60 71 menu item (do not add a `Generic Setup Tool`). Then go to the newly 61 72 created `portal_setup` tool and run the upgrades. Before the upgrade … … 63 74 it should be "3.4.0". 64 75 65 2. Go to the "Profiles" tab, make sure "CPS Default" is selected and 76 2. Importing the profiles 77 78 Go to the "Profiles" tab, make sure "CPS Default" is selected and 66 79 press import. Importing this profile takes some time, and results 67 in a working CPS site. 80 in a working CPS site. 68 81 69 82 As with all previous CPS upgrades, installing the default profile … … 73 86 installation will also remove any custom objects. 74 87 75 3. CPS 3.4 has it's member folder in <portal>/members, where CPS 3.2 88 3. Taking care of the member folder 89 90 CPS 3.4 has it's member folder in <portal>/members, where CPS 3.2 76 91 and 3.3 had it in <portal>/workspaces/members. You need to change 77 92 the configuration back to the old path. Open the portal_membership … … 80 95 path will be changed back every time you import a profile. 81 96 82 4. Go to the Profiles tab of the portal_setup tool. Select and install 97 4. Other products and legacy products 98 99 Go to the Profiles tab of the portal_setup tool. Select and install 83 100 the profile for any of the products you used. If you had 84 101 notifications set up in your old site, you will want to install the … … 91 108 are now the new replacement products CPSSharedCalendar and 92 109 CPSMailAccess, which you probably would want to use instead. See 93 their respective documentation on how to install and migrate from 110 their respective documentation on how to install and migrate from 94 111 old versions. 95 112 96 5. In some cases installing profiles may enable upgrades that were not 113 5. Multiple upgrades 114 115 In some cases installing profiles may enable upgrades that were not 97 116 previously enabled. Go to the "Upgrades" tab and run any upgrades 98 117 that now are enabled. 99 118 100 6. Lastly, and this is a good idea to do after any configuration 101 change, you should go to portal_setup and create a new snapshot. 119 6. Last problems, the customizations 120 121 If you still encounter problems after all those steps, the problems might 122 come from customized versions of the ZPT (.py) or Python scripts (.py) 123 present in your custom product(s). For example your product(s) might 124 have customized `CPSSchemas/skins/cps_schemas/widget_attachedfile_render.pt` 125 or any such file. The solution is to remove those customizations until you 126 find the one(s) being the cause. Often those customizations can be removed 127 since CPS has evolved and improved and you might prefer the current 128 implementation in CPS. If it's not the case those customizations have to be 129 upgraded to the current state of CPS. 130 131 7. Backing up the configuration with a snapshot 132 133 Lastly, and this is a good idea to do after any configuration 134 change, you should go to portal_setup and create a new snapshot. 102 135 This way you can back out of any configuration changes. For example, 103 136 if you make a snapshot before you install a product, you can
