QA Feature Specification:Calendar Migration: Difference between revisions

mNo edit summary
Line 10: Line 10:
*iCal.app (on Mac)
*iCal.app (on Mac)
*Evolution
*Evolution
The Migration Wizard will appear as soon as there are no calendars registered. This means on running Sunbird > 0.2 the first time (in that particular profile) or after deleting all calendars from the calendars tab.


With all of these, expect that the migration utility should be able to import the various calendars including the event and task data from those calendars. I will note some extra items that will or will not be imported below, and this should be considered expected behavior.
With all of these, expect that the migration utility should be able to import the various calendars including the event and task data from those calendars. I will note some extra items that will or will not be imported below, and this should be considered expected behavior.
Line 23: Line 25:
* iCal.app calendar names will not be imported
* iCal.app calendar names will not be imported
* Evolution calendar names will not be imported. But, events imported from evolution should have timezone information specified.
* Evolution calendar names will not be imported. But, events imported from evolution should have timezone information specified.
=== Enabling migration debugging ===
If you encounter any problems with migration, you can turn on additional debugging code, which may give more information useful to fix the error.  To do this:
# Open Options/Preferences (The name and location will vary based on your OS.)
# Go to Advanced
# Open the Config Editor
# Create a new boolean pref named <tt>calendar.migration.log</tt> and sets its value to <tt>true</tt>.
# Re-try your migration.  Additional information will now be reported in the Error Console (under Tools).
188

edits