yeah, I routed the engine in the main application routes as follows:
mount MyEngine::Engine => '/myengine'
and rake routes shows it as mounted as expected, it just doesnt
actually let you access it when running the server.
On Jul 7, 5:09 pm, Juan Manuel Barreneche
<juanmanuel.barrene...@gmail.com> wrote:
> Hi!
>
>
>
> On Thu, Jul 7, 2011 at 12:10 PM, mrloz <jonathan.lozin...@gmail.com> wrote:
> > Hi there.
>
> > I'm having some real issues with engines and rc4:
>
> > 1: generators are broke
>
> > rails plugin new myengine --mounable
> > cd myengine
> > rails g
> > <broken>...
> > 2: after you build an engine and gem it up, if you do:
>
> > rails new myproject
> > add gem 'myengine' to Gemfile
> > add mount MyEngine::Engine => '/myengine'
> > rake routes:
>
> > myengine /myengine {:to=>MyEngine::Engine}
>
> > then rails s
>
> > visithttp://localhost:3000/myengine
>
> > error log:
>
> > Started GET "/myengine" for 127.0.0.1 at Thu Jul 07 16:07:11 +0100
> > 2011
> > ActionController::RoutingError (No route matches [GET] "/myengine"):
>
> > This is really odd, as rails 3.0 engines worked just fine on rails3.0,
> > however my namedspaced rails3.1 engine wont (and cant run on 3.0 as
> > isolate namespace is 3.1 only)
>
> > What can I do. Currently setting to edge-rails gets bundle failures
> > on actionpack (3.2.0.beta) etc...
>
> > Thanks
>
> I dont know about the first issue.
> But, did you add any route to your engine? (you don't need to bundle or make
> a gem of your engine, in the path: test/dummy you've got a test app)
>
> Juan Manuel Barreneche
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To post to this group, send email to rubyonrails-core@googlegroups.com.
To unsubscribe from this group, send email to
rubyonrails-core+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/rubyonrails-core?hl=en.
