Engine broke under rails 1.1.6

Rails Engines
1

ActionController::RoutingError (Recognition failed for “/user/signup”):

All the controller in Engine can not be recognized,I update my engine to
the latest version,the application even can not be started.Something
more need to be done?

2

George wrote:

ActionController::RoutingError (Recognition failed for “/user/signup”):

All the controller in Engine can not be recognized,I update my engine to
the latest version,the application even can not be started.Something
more need to be done?

http://npenkov.com/articles/2006/08/14/engines-with-rails-1-1-5-6-routing-issue
and
http://svn.rails-engines.org/engines/branches/rb_1.1

still can not work,both the patches lead to the webrick’s direct exit

3

This issue have already been fixed in trunk version of engines. My
recomndation is not to use my patch, because it will not be supported in
next versions of engines. It was only temporary solution for my
application to run with Rails 1.1.6 and I decided to share it.
Insted checkout trunk of engines - I have already created a new
application with User and Login engines, and it works fine with latests
(TRUNK) from engines.

George wrote:

George wrote:

ActionController::RoutingError (Recognition failed for “/user/signup”):

All the controller in Engine can not be recognized,I update my engine to
the latest version,the application even can not be started.Something
more need to be done?

http://npenkov.com/articles/2006/08/14/engines-with-rails-1-1-5-6-routing-issue
and
http://svn.rails-engines.org/engines/branches/rb_1.1

still can not work,both the patches lead to the webrick’s direct exit

4

FYI, the latest engines version is not in the SVN ‘trunk’ (that’s for
ongoing development, and is currently broken), but is available via an
SVN tag: http://svn.rails-engines.org/engines/tags/rel_1.1.4. It is
also available via script/plugin as usual. Likewise, the ‘:edge’ flag
is not required with Rails 1.1.4. Please see my earlier emails on the
Rails list for more information.

Engines will not currently work with ‘Edge Rails’ (their SVN trunk),
since there seems to be some major refactoring going on.

  • James
5

Is this still the case? Any anticipated time when engines will again
work with edge?

Thanks,

Steve

James A. wrote:

Engines will not currently work with ‘Edge Rails’ (their SVN trunk),
since there seems to be some major refactoring going on.

  • James
6

One more think:

when checking out engines trunk version - set in your environment:
module Engines
config :edge, true
end

Nick Penkov wrote:

This issue have already been fixed in trunk version of engines. My
recomndation is not to use my patch, because it will not be supported in
next versions of engines. It was only temporary solution for my
application to run with Rails 1.1.6 and I decided to share it.
Insted checkout trunk of engines - I have already created a new
application with User and Login engines, and it works fine with latests
(TRUNK) from engines.

George wrote:

George wrote:

ActionController::RoutingError (Recognition failed for “/user/signup”):

All the controller in Engine can not be recognized,I update my engine to
the latest version,the application even can not be started.Something
more need to be done?

http://npenkov.com/articles/2006/08/14/engines-with-rails-1-1-5-6-routing-issue
and
http://svn.rails-engines.org/engines/branches/rb_1.1

still can not work,both the patches lead to the webrick’s direct exit

7

I’m also wondering about this. Am trying to build an engine by
extracting
code from a RESTful-based app, so it has to work on Edge for me.

Thanks,
Casper