The problems stem from the strange way that Rails has been require-ing controllers within modules. Old (1.0.0, 1.0.1) versions of the Engines plugin would strip everything bar the filename out of the require path in order to quickly do the code mixing, but that also removes module information (since ActiveRBAC::UserController would be required as 'active_rbac/user_controller'). The biggest problem is that different installations of Rails seem to use different paths when require-ing controllers. That's what I've spent the last 3 point-releases chasing.
The current version of the Engines plugin (1.0.6) *should* fix all of these problems - if you find you're having problems then post here (preferrable with traces from the engine logger; see Engines.log for details about how to turn it on) and we'll work through it. - james On 2/3/06, Manuel Holtgrewe <[EMAIL PROTECTED]> wrote: > Hi > > I'm currently working on making ActiveRBAC (https:// > activerbac.turingstudio.com) into an engine. > > However, there seems to be a problem with Controllers and Namespaces. > I want my controller to be in the "ActiveRBAC" namespace since > ActiveRBAC contains controllers with more or less common names such > as "UserController". > > A quick look at the mail archive shows me that there are known > problems. Could someone give me an abstract of the problems? How much > work would it be to add namespace support for controllers to rails- > engines? I'd be willing to give it a try, then. > > Regards > > Manuel Holtgrewe > _______________________________________________ > engine-developers mailing list > [email protected] > http://lists.rails-engines.org/listinfo.cgi/engine-developers-rails-engines.org > -- * J * ~ _______________________________________________ engine-developers mailing list [email protected] http://lists.rails-engines.org/listinfo.cgi/engine-developers-rails-engines.org
