Forum: Ruby on Rails Re: Login Engine Missing Source

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
5652538ef541d6e3a3d3a8936a83bd42?d=identicon&s=25 Marcus Felix Wendt (Guest)
on 2006-03-06 11:28
(Received via mailing list)
Yes, engines is installed. Using the dispatcher.cgi I can see the
standard login page - switching to dispatcher.fcgi in .htaccess brings
the before mentioned error.

I also followed the guidelines in the login_engine README  and changed
environment.rb,  application.rb, application_helper.rb etc.

- m



Am 06.03.2006 um 10:55 schrieb James Adam:

Can you confirm that you've also installed the engines plugin?

  script/plugin install engines

or

  svn co http://svn.rails-engines.org/plugins/engine


- james

On 3/6/06, Marcus Felix Wendt <lists@marcuswendt.de> wrote:
Hi!

I'm new to Rails and Ruby, so this might be a simple question. I wrote a
simple blog-application using Rails 1.0 and installed login_engine to
add some authentication mechanisms. After following the installation
procedure I get this error when dispatching via FastCGI (ordinary CGI
works):

MissingSourceFile in <controller not set>#<action not set>

no such file to load -- login_engine

I repeated the procedure a few times, even starting with a blank new
rails app - it's always the same. Btw. I'm working on OS X 10.4
Can anyone please point out the problem? How can it come that
vendors/plugins isnt loaded - isnt this in the default load path?

Thanks in advance

Marcus
_______________________________________________
Rails mailing list
Rails@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails



--
* J *
  ~
_______________________________________________
Rails mailing list
Rails@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails
This topic is locked and can not be replied to.