OK, so after mentioning it in my last post, I’ve decided to go ahead and implement it. Comatose version 0.7.1 adds a
DEFER_COMATOSE_LOAD flag that you can use to, well, defer comatose’s loading. You will have to manually tell it to load in your
See this devblog post for more.
Normally, I’d only post this on the Comatose development blog, but I wanted to make sure anybody who’s having problems using Comatose with other plugins/applications knows about this. If you have problems or questions, leave a comment here. Thanks!
This release finally adds support for versioning. It also adds an auto-loader for any comatose customizations you put in a
See the devblog post for more.
Comatose has been having a few problems co-existing with some kinds of plugins lately. The problems seem to be caused, at least in part, because the comatose controllers extend
ApplicationController and therefore
application.rb before the rest of the plugins load.
Plus, some plugins seem to take issue with any previous plugins defining an Active Record model before they’re loaded — very picky stuff.
To combat this, I’m thinking of adding a
DEFER_LOADING flag in
comatose/init.rb. When the plugin initializes, if that flag is
true it won’t load the controllers or the models. You’ll then need to add a call to
Comatose::Load in your
environment.rb that would then load the controllers and models — after the rest of your app had loaded. By default, the flag will be set to
false so that it remains backward compatible.
Look for that in the next release.