# Migrating to 1.2

**URL:** <https://www.ruby-forum.com/t/migrating-to-1-2/81249>\
**Category:** Engines\
**Created:** [January 6, 2007, 7:30pm UTC](https://www.ruby-forum.com/t/migrating-to-1-2/81249 "2007-01-06T19:30:40Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![James\_Nelson](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/977dab/32.png) [@James\_Nelson](https://www.ruby-forum.com/u/James_Nelson)\
**Post date:** [January 6, 2007, 7:30pm UTC](https://www.ruby-forum.com/t/migrating-to-1-2/81249/1 "2007-01-06T19:30:40Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![James\_Nelson](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/977dab/32.png) [@James\_Nelson](https://www.ruby-forum.com/u/James_Nelson)\
**Post date:** [January 19, 2007, 4:30pm UTC](https://www.ruby-forum.com/t/migrating-to-1-2/81249/2 "2007-01-19T16:30:35Z")

</div>

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](http://dev.rails-engines.org/tickets/258)  
for more details.

- James