# Rails 1.1.3 and routes to controllers in directories **URL:** \ **Category:** Rails\ **Created:** [June 28, 2006, 4:43pm UTC](https://www.ruby-forum.com/t/rails-1-1-3-and-routes-to-controllers-in-directories/96397 "2006-06-28T16:43:52Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![thijs](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/t/a4c791/32.png) [@thijs](https://www.ruby-forum.com/u/thijs)\ **Post date:** [June 28, 2006, 4:43pm UTC](https://www.ruby-forum.com/t/rails-1-1-3-and-routes-to-controllers-in-directories/96397/1 "2006-06-28T16:43:52Z")
Hi, All my controllers in subdirectories aren’t reachable by the normal urls anymore since my upgrade to 1.1.3. 404 errors. Did anybody else experience this? grtz Thijs ---
**Author:** ![thijs](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/t/a4c791/32.png) [@thijs](https://www.ruby-forum.com/u/thijs)\ **Post date:** [June 28, 2006, 4:57pm UTC](https://www.ruby-forum.com/t/rails-1-1-3-and-routes-to-controllers-in-directories/96397/2 "2006-06-28T16:57:04Z")
On 6/28/06, Thijs C. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > Hi, > > All my controllers in subdirectories aren’t reachable by the normal urls > anymore since my upgrade to 1.1.3. 404 errors. Did anybody else > experience this? I’m having the same error. Haven’t found a solution yet. ---
**Author:** ![thijs](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/t/a4c791/32.png) [@thijs](https://www.ruby-forum.com/u/thijs)\ **Post date:** [June 28, 2006, 5:02pm UTC](https://www.ruby-forum.com/t/rails-1-1-3-and-routes-to-controllers-in-directories/96397/3 "2006-06-28T17:02:44Z")
I meant to say Routing errors instead of 404 errors by the way. I was affraid it might be a new bug. At least it’s possible to still bind the app to 1.1.2 nowadays. ---
**Author:** ![thijs](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/t/a4c791/32.png) [@thijs](https://www.ruby-forum.com/u/thijs)\ **Post date:** [June 28, 2006, 5:05pm UTC](https://www.ruby-forum.com/t/rails-1-1-3-and-routes-to-controllers-in-directories/96397/4 "2006-06-28T17:05:26Z")
[http://www.ruby-forum.com/topic/70990](http://www.ruby-forum.com/topic/70990) About the same problem… ---
**Author:** ![thijs](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/t/a4c791/32.png) [@thijs](https://www.ruby-forum.com/u/thijs)\ **Post date:** [June 28, 2006, 5:12pm UTC](https://www.ruby-forum.com/t/rails-1-1-3-and-routes-to-controllers-in-directories/96397/5 "2006-06-28T17:12:49Z")
On 6/28/06, Thijs C. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > I meant to say Routing errors instead of 404 errors by the way. > > I was affraid it might be a new bug. At least it’s possible to still > bind the app to 1.1.2 nowadays. Yes that is a very nice ability. I’ve revisted the routing docs to see if anything had changed, but it doesn’t appear that way. Just going to stick with 1.1.2 until I hear otherwise. ---
**Author:** ![thijs](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/t/a4c791/32.png) [@thijs](https://www.ruby-forum.com/u/thijs)\ **Post date:** [June 29, 2006, 11:11am UTC](https://www.ruby-forum.com/t/rails-1-1-3-and-routes-to-controllers-in-directories/96397/6 "2006-06-29T11:11:24Z")
Brian H. wrote: > Anyone submit a ticket for this yet? > > Check this out… > > Say I have /admin/foo > > If I go to that, I get a routing error. > > If I go ot /admin then I also get a routing error. > > But if I go to /admin/foo again… it works! > > Sounds like a bug to me. I have exactly the same behavior … ---
**Author:** ![thijs](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/t/a4c791/32.png) [@thijs](https://www.ruby-forum.com/u/thijs)\ **Post date:** [June 28, 2006, 5:35pm UTC](https://www.ruby-forum.com/t/rails-1-1-3-and-routes-to-controllers-in-directories/96397/7 "2006-06-28T17:35:21Z")
Anyone submit a ticket for this yet? Check this out… Say I have /admin/foo If I go to that, I get a routing error. If I go ot /admin then I also get a routing error. But if I go to /admin/foo again… it works! Sounds like a bug to me.