Removing class redefiniton in 'add comatose support' migration?

[Lena Herrmann]

Hi!

Has anyone ever reported the following problem:

The class ComatosePage gets overwritten in the 'add comatose support'
migration, to make sure the comatose root page can be created. But if
you have another migration following this one, where you create a
couple of comatose pages, they still are instances of that overwritten
class. Especially the before/after filters from the original
ComatosePage aren't evaluated. This results in the slugs being nil, a
quite confusing error when you don't know where to look.

I've been using comatose in the second project now. In the first one,
we came up with a solution similar to aslakjo's - defining a class
ComatoseRootPage. In the current project, we found a much easier way
of solving this: remove the class redefinition altogether, for the
root page just do ComatosePage.new(...).save(false).

See here:
http://github.com/lenalena/comatose

This is not really an official patch as I couldn't get the tests up
and running (error message being: "./test/functional/../test_helper.rb:
3:in `require': no such file to load -- /Users/config/environment.rb
(LoadError)")

I can see there aren't many pull requests being made or being answered
in comatose, but I think it would be great to tackle this problem some
way or the other?

Cheers!
Lena