Forum: Rails Engines MissingSourceFile: no such file to load -- login_engine

4e25326d3e557403cd65c4194144d90e?d=identicon&s=25 Eli Miller (jqr)
on 2006-06-21 16:57
This error seems to stem from the require line in application.rb. I'm
new to Rails, but I'm assuming that this should load the
lib/login_engine.rb from within the vendor/plugins/login_engine
directory.

I've been over the install docs several times and followed along with
the login engine demonstration video. I must have missed something
crucial along the way but  I can't find it. Any idea what it might be?


$ ruby --version
ruby 1.8.4 (2005-12-24)

$ rails --version
Rails 1.1.2

both engines and login_engines have been installed with script/plugin
today
4e25326d3e557403cd65c4194144d90e?d=identicon&s=25 Eli Miller (jqr)
on 2006-06-21 17:03
I suppose I should add, this is the error I get when accessing

http://localhost:3000/user/login/


MissingSourceFile

no such file to load -- login_engine

RAILS_ROOT: script/../config/..
Application Trace | Framework Trace | Full Trace

/usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:21:in
`require__'
/usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:21:in `require'
/usr/lib/ruby/gems/1.8/gems/activesupport-1.3.1/lib/active_support/dependencies.rb:147:in
`require'
#{RAILS_ROOT}/app/controllers/application.rb:4
-e:4

This error occured while loading the following files:
   application.rb
   login_engine
4e25326d3e557403cd65c4194144d90e?d=identicon&s=25 Eli Miller (jqr)
on 2006-06-21 19:14
Problem Solved:

Server needs to be restarted after any edits to environments.rb
8532c8cda53864f7140ade70c810f57c?d=identicon&s=25 Sulabh Jain (sulabhjain)
on 2009-02-18 00:42
Eli Miller wrote:
> Problem Solved:
>
> Server needs to be restarted after any edits to environments.rb

Solution to the problem that worked for me:
............................................

When you go to http://localhost:3000/ page then click on the "About your
application environment" link to see if the things are working for you.

If it says about the sqlite3 missing problem then you need to install
sqlite3 plugin using gem. I got the problem using sqlite3 as well as
mysql.

Using mysql(mysql installed in advance)
created application using : rails -d mysql demo
you need to make appropriate changes to config/database.yml file such as
user name ( I kept the user name as root while configuring mysql) and
password of the "development environment" only( no need to do anything
in production or test) as well provide the name of the database which
you can create using mysql client.

mysql>CREATE DATABASE mydiary;

I hope the same applies using sqlite3.

Thanks,
Sulabh Jain
This topic is locked and can not be replied to.