Hi James, Well spotted - this was a result of the fact that plugins can be 'enginized' as part of the plugin loading process now, which occurs before routing is started up. Previously this wasn't an issue because Engines.start was called after routing was configured. There's a fix in the release branch; see http://dev.rails-engines.org/tickets/258 for more details.
- James On 1/5/07, James Nelson <[EMAIL PROTECTED]> wrote: > Hi there > > I've been trying to move my rbac plugin over to the new rails. So far its > worked pretty well - all my models work from the console, and after swapping > configuration over to class variables that all still works. The biggest > problem is that all my old routes don't work. I've got a user controller for > example, with a login action. I used to go to /user/login and the login > action would be run (as you'd expect) - this worked with the default rails > routes. However, now /user/login generates a routing error telling me it > doesn't exist. Is there anything i'm supposed to do with the new version? > > -- > - James > _______________________________________________ > engine-users mailing list > [email protected] > http://lists.rails-engines.org/listinfo.cgi/engine-users-rails-engines.org > > > -- * J * ~ _______________________________________________ engine-users mailing list [email protected] http://lists.rails-engines.org/listinfo.cgi/engine-users-rails-engines.org
