ChiliProject is not maintained anymore. Please be advised that there will be no more updates.
We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.
Double initial journal for migrated wiki history (Bug #542)
The initial journal is created twice for objects that were
acts_as_versioned (in core: WikiContents), once in the migration to create initial journals for activity-providing models (source:/db/migrate/20100714111653_build_initial_journals_for_acts_as_journalized.rb) and once in the migration to convert WikiContentVersions to Journals (source:/db/migrate/20100804112053_merge_wiki_versions_with_journals.rb).
The least sucky way to work around that would be to test the objects providing activity (first migration) if they include ActsAsVersioned and not "add" an initial journal as it is already provided by acts_as_versioned, that leaves us with data that's already been migrated with the faulty migration. For core, that concerns only the WikiContents, and as those don't have a
created_at attribute, the corresponding initial journals created in the migration didn't get backdated, i.e. the newest initial journal is the wrong one.
Ok, as there is absolutely no way to find out which
acts_as_activity models also were
acts_as_versioned, Holger proposed to migrate only objects of the core classes in the core migration and to document how to upgrade to ChiliProject 2.x for plugin authors that have