search for: resolve_controller

...ave probably overlooked something here, but it appears to me that something is missing to be able to route to those nested controllers. Looking in Merb::Dispatcher, it looks like the workflow goes like this. route = route_path(request_uri) route_path then calls Merb::Router.match(path) klass = resolve_controller(route[:controller]) resolve_controller then splits the controller part of the route with segments = controller_name.split(''/'').map{|s| s.snake_case} However, it appears that Merb::Router.match isn''t handing back "module/class". For example: If I setup say...

I have no problems loading any static requests, but any that are routed to a controller blow up. I''m getting a ''Bad controller'' error. The reason I''m a bit flummoxed is because the stack trace makes no sense. It terminates on this line: resolve_controller 68 /opt/local/lib/ruby/gems/1.8/gems/merb-0.3.7/ lib/merb/merb_dispatcher.rb As you can see, this is in the merb-0.3.7 gem, but earlier in the stack trace I can see this: run 290 /Users/lukesutton/Pending/merb_test/framework/lib/merb/ server.rb So, even though I''m running merb...