MIGRATE.txt CalendarX 0.5.3(dev) March 26 2005 (last modified for CalendarX 0.5.2) by +lupa+ (lupaz on sf.net, lupa at zurven dot com) Released under the GPL (see LICENSE.txt) MIGRATION from 0.4 branch to 0.5 branch: Don't migrate so much as create anew. Actually, there are very many code changes for this branch of CalendarX and it may "break" your old ones. Actually, I'm fairly certain that simply putting this CalendarX into your Products folder, restarting or refreshing the product and expecting your existing CalendarX instances to work is futile. They will not work. However, you should be able to install this branch and create a new CalendarX instance and configure it to work like the old one did... some of the property sheet info has moved around, but the basic procedure is the same. So if you have a live Production 0.4 branch CalendarX site, don't jump right into this and expect the seamless upgrade that comes from an alpha release to a beta or stable branch release. But it still reads all the standard Plone events just likebefore, so you should be able to get a working CalendarX instance up withinminutes configured like your old one. So put up a "Construction" sign on your Production website while you do this. And, of course, back up your Data.fs first. But you always do that anyway, right? I knew you did. OLD (0.4 branch) INSTRUCTIONS I. Upgrading from 0.4 branch versions of CalendarX. II. Upgrading from 0.2 branch versions of CalendarX. III. Upgrading from 0.1 branch versions of CalendarX. IV. When you've upgraded your Zope. (added 0.4.5) I. Upgrading to from 0.4 branch versions of CalendarX. 1. Replace the old version of CalendarX in your INSTANCE_HOME/Products folder with the new version of CalendarX (0.4 or higher). 2. Restart Zope, or in the ZMI you can go to Control Panel, Product Management, CalendarX, and in the Refresh tab, click Refresh. Or in Plone (2.0+), go to Plone Setup, Add/Remove Products, and under "Installed Products", look for CalendarX and click the link that says "This product has been upgraded, click here to reinstall." 3. Any parts of CalendarX that you have customized should be compared with fresh versions (and the HISTORY.txt file) to see if there are changes that you should be aware of in your customizations. If all you have changed are the CX_props_XXX property sheets, then there is little chance of any problems. 4. There is not currently, nor immediate plans to create, an automated upgrade feature that will migrate your configurations to the new versions of the property sheets, etc. This is because CalendarX is designed to allow easy TTW access to all the scripts and templates for customization, and any one CalendarX installation will be expected to have many customization choices that an automated upgrade mechanism will not properly handle. Document the changes you make so that you can more easily upgrade to newer versions of CalendarX. II. Upgrading from 0.2 branch versions of CalendarX. Question: I looked through all the docs and I don't see any instructions on how to migrate from version 0.2.13 to 0.4.3. Since you can't use the quickinstaller to remove 0.2.13 from Plone, will 0.4.3 simply overwrite 0.2.13 or do you have to manually remove files from the file system? Answer: Ah, migration. It really isn't much problem, although it is not perfectly transparent. 1. Leave your current (old) calendar in place for now. The two can run concurrently if you wish, until the new one is all set up. Or forever (I have both running as demos at calendarx.org). 2. All the files for the 0.2.13 branch are stored in the instance folder, so they will not interfere with the new one at all. When you're done with 0.2.13, just delete that folder. 3. Install 0.4.3 as per instructions (untar, unzip in /Products, restart Zope, use QuickInstaller to add CalendarX to your Plone site. Then (in Plone), use the dropdown to add a CalendarX instance to your Plone site. Name it whatever you want. You can change the name later in the usual Plone way. 4. Customize your CalendarX in approximately the same way that you did before (with 0.2.13) except that now it's more Plone-ish... you go to portal_skins/CalendarX and find the property sheet that you want to alter, hit Customize and then change the Properties in the Properties tab. You can likewise customize any of the property sheets, the macros, the templates, the scripts. THERE IS NO MECHANISM FOR DIRECT MIGRATION from the old 0.2.13 property sheets to the new ones. Most of the properties have the same names though, so it should be fairly easy. 10 minutes tops to migrate if all your customizing has been in the property sheets. 5. You can leave these property sheets in your /custom folder, or you can use the ZMI and cut/paste them into your CalendarX instance folder so that they are out of the way. 6. If you want more than one CalendarX instance, you will definitely want to use the ZMI and cut/paste your property sheets into the local instance folders... that way each calendar has its own look, feel, and behavior (what events it locates, etc.). Hope that helps. III. Upgrading from 0.1 branch versions of CalendarX. Ugh. No idea at this moment. Probably a bit like the ones above. Sorry, but write me if you are having trouble. Don't upgrade, just replace the olde one and start fresh. IV. When you've upgraded your Zope. (added 0.4.5) I still don't know exactly what the problem is, but when I upgraded my Zope to 2.7.3, I find that my events are being stored with the start/end dates in Universal time instead of GMT-4 (eastern U.S.A., where my server is located. This causes some funny time-shifting because older events that have a start time in the late evening show up on the following day. I think (uninformed thinking here) that start/end should be stored internally in Universal time, and reformatted to local time for the calendar IF SO DESIRED BY THE CALENDAR ADMINISTRATOR. That makes more sense to me... I think. Or not. Ten-to-one this is a configuration problem that I didn't set properly. I'll remove this comment and explain it properly when I learn the real problem, which I'm fairly certain is in my OS and not my Zope.