Migration error importing from old version of redmine to Chiliproject v2.0 (Bug #508)

BTW, when going into chiliproject 2.0.0, acts_as_versioned plugin is no longer there, so the migrate quits with:

undefined method `acts_as_versioned' for #<Class:0x7f64c4af48f0>

----
Unless I put that plugin back to ensure a successful migration.

(What the hell, I'm pretty sure I had posted here!?)

acts_as_versioned has been replaced by acts_as_journalized, if you get errors of some code calling acts_as_versioned in 2.0, you either have a plugin that needs upgrading, or some files haven't been upgraded correctly on your installation. I just checked on my local development 2.0 installation, and there's no mention of acts_as_versioned.

After poking around, acts_as_versioned is needed by the ezfaq_plugin (and gloc?) from the old install. I removed all traces of faq from the sqldump by hand, which means quite a bit of a data loss on my side, and the import works fine (with the exception of the projects.projects_count error, that still happens).

It looks like the latest greatest copy of ezfaq needs acts_as_versioned:

https://github.com/ansoncat/ezfaq_plugin/blob/master/app/models/faq.rb

So will adding acts_as_versioned plugin affect chilliproject in a bad way?

Wari Wahab wrote:

After poking around, acts_as_versioned is needed by the ezfaq_plugin (and gloc?) from the old install.

I think gloc is the way way old way of doing translations in rails pre-2.3 (and probably even pre-that), i.e. that shouldn't be needed anymore.

I removed all traces of faq from the sqldump by hand, which means quite a bit of a data loss on my side,

I don't think the data bothers anyone when it's in the database and in its own tables and so on. One way to revert migrations from plugins (if those plugins are coded correctly): rake db:migrate:plugin NAME=redmine_ez_faq VERSION=0 (that's from memory but should at least resemble the correct version…), this way you don't have to remove it by hand…

and the import works fine (with the exception of the projects.projects_count error, that still happens).

Mmh, the only mention I can find it is in the setup and a later migration in which projects_count is removed. In other words, it shouldn't be there, and probably even not any more in Redmine 0.8. Now, the error you have seems to come from some part of your install still trying to read it, so either some of your files haven't been upgraded properly, or a plugin is looking for it. Anyway, you know the drill ;-)

It looks like the latest greatest copy of ezfaq needs acts_as_versioned:

https://github.com/ansoncat/ezfaq_plugin/blob/master/app/models/faq.rb

So will adding acts_as_versioned plugin affect chilliproject in a bad way?

Well, even if adding acts_as_versioned back doesn't cause any immediate problem, it will only postpone it.

Now, and take all that with a huge grain of salt as I haven't tried or tested any of this: adding it back probably won't hurt, but you might get funny errors on the activity page, and the faq activity entries will not show. Can't guarantee nothing else won't break either.

I've added Tim (who wrote most of the acts_as_journalized code) and Eric (spent enough time with the code ;-) ), maybe they can/want to chime in too.

Eric: I think we should also make a page for plugins that are known to not work.

Eric Davis wrote:

I think we should also make a page for plugins that are known to not work.

Good idea. We can do simple lists of "Untested", "Known working" (or "Known working at this fork"), and "Not working". This would also be good to have a plugin directory for…

See Plugin Compatibility, I started the list the other way round though (Plugin > Version > compatible with), as most of the time you don't want to plodge through the whole history of ChiliProject to look for the plugins you're interested in.

and the import works fine (with the exception of the projects.projects_count error, that still happens).

Mmh, the only mention I can find it is in the setup and a later migration in which projects_count is removed. In other words, it shouldn't be there, and probably even not any more in Redmine 0.8. Now, the error you have seems to come from some part of your install still trying to read it, so either some of your files haven't been upgraded properly, or a plugin is looking for it. Anyway, you know the drill ;-)

Thing is, all I did to get the error is to just:

• git clone chiliproject
• mysql -p -u chiliproject < olddump.sql
• rake db:migrate # projects_count error
• rake db:migrate # error goes away

Wari Wahab wrote:

Thing is, all I did to get the error is to just:

• git clone chiliproject
• mysql -p -u chiliproject < olddump.sql
• rake db:migrate # projects_count error
• rake db:migrate # error goes away

See Eric's answer in the second paragraph of note 5 about this. It's "normal" that it happens the first time because you're coming from a fairly old Redmine, and it's "normal" that it works the second time, it goes on from where it left and broke the first time.

Thanks for the clarification. So far, the installation looked fine on my side, sans the ezfaq plugin. I'm getting people to test it out.

I'm not sure about the ezfaq bit though, but if a patch to ezfaq is as simple as replacing acts_as_versioned to acts_as_journalized it would be great, but I doubt it would be that easy, right?

Wari Wahab wrote:

I'm not sure about the ezfaq bit though, but if a patch to ezfaq is as simple as replacing acts_as_versioned to acts_as_journalized it would be great, but I doubt it would be that easy, right?

1. not that easy,
2. as I said, I won't do it unless there is a maintainer committed to the plugin, even better if he is committed to maintaining it not only for Redmine.