upgrading 0.8.3 -> 0.8.4

Created by . Last modified on 2003/08/01.

This is a rather short one; I assemble some gotchas you proably want to avoid when upgrading to Silva-0.8.4.

• some bug has slipped in silva0.8.4; better first apply the fix to the /silva_upgrade_0.8.4/import/from-0.8.3-to-0.8.4/service_widgets/top/table/mode_view/render before You trigger the upgrade script.
• if you upgrade multiple Silva instances within the same Zope: rename the created backup folder in /silva_upgrade_0.8.4/backup/from-0.8.3-to-0.8.4 after each update, or the backups of the updates get intermangled (you get a lot of copy_ there)
• if You do not have the Groups product installed, You may run into problems with the import of the upgrade: PROBLEM(100) ZODB Could not import class 'ZGroupsService' from module 'Products.Groups.ZGroupsService'

  (This message only shows up in the zLOG, not in the ZMI!)

  Actually this error message is harmless; You do not get the service_groups registry imported you do not need anyway..

  However if You install groups later on, You have to add this registry by hand.

• if You get the similar error message PROBLEM(100) ZODB Could not import class 'ZGroupsService' from module 'Products.Groups.ZGroups'
  despite You have the Groups installed this means the upgrade contained some wrong class.
  Instead change to the Folder silva_upgrade_0.8.4 and add a service_groups of type Groups Service by hand.
• the folder /silva/images is copied away from this upgrade, despite the /silva/images/Attention_Silva_users_README somewhat promised differently. Just look it up in the backup directory, if somewhat is missing.
• if You use the method activate_security_hack somewhere in Your widgets, replace it by security_trigger (Use the Find tab of the created backup directory, or of Your custom registry directories to search for this string. Replacement has to be done by hand, unforatunately -- unless someone writes a script to do this ;-)
• do not forget to reregister your custom content types after the upgrade. (Maybe you want to call the corresponding scripts already within the update by editing the update script.)