Rails 1.1.3 and routes to controllers in directories

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

On 6/28/06, Thijs C. [email protected] 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.

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.

http://www.ruby-forum.com/topic/70990

About the same problem…

On 6/28/06, Thijs C. [email protected] 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.

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 …

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.

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs