Ruby on Rails
Friday, March 28, 2014
Please help. I am stumped.
I have four engines inside a rails application. The cucumber scenarios run just fine in three of the engines. The fourth fails with the error:
No route matches [GET] "/stylesheets/common_engine/application.css" (ActionController::RoutingError)
/usr/local/ruby-1.9.3/lib/ruby/gems/1.9.1/gems/actionpack-3.2.17/lib/action_dispatch/middleware/debug_exceptions.rb:21:in `call'
I can not see any significant differences between configuration files of the applications that work and this one.
The test/dummy application runs just fine ($ rails server) with RAILS_ENV set to either 'development' or 'test'.
All applications/engines are running ruby 1.9.3, rails 3.2.17, and cucumber 1.3.10. Google did not help.
Thank you.
-- I have four engines inside a rails application. The cucumber scenarios run just fine in three of the engines. The fourth fails with the error:
No route matches [GET] "/stylesheets/common_engine/application.css" (ActionController::RoutingError)
/usr/local/ruby-1.9.3/lib/ruby/gems/1.9.1/gems/actionpack-3.2.17/lib/action_dispatch/middleware/debug_exceptions.rb:21:in `call'
I can not see any significant differences between configuration files of the applications that work and this one.
The test/dummy application runs just fine ($ rails server) with RAILS_ENV set to either 'development' or 'test'.
All applications/engines are running ruby 1.9.3, rails 3.2.17, and cucumber 1.3.10. Google did not help.
Thank you.
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/0d3cb976-f6c2-4bc3-a464-5aa990870948%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment