Forum: Ruby on Rails Running rails 1.2.2 in \vendor\rails problems

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.
82c59780911721f5cbe82d3111313519?d=identicon&s=25 Giant Cranes (giantcranes)
on 2007-02-08 18:25
Hi,

I am trying to move from gem rails to edge rails (well, 1.2.2 with a
patch). I have been running gem rails 1.2.2 successfully.

When I do a svn:externals to tag rel_1-2-2
[http://dev.rubyonrails.org/svn/rails/tags/rel_1-2-2/] the rails code is
placed in  \vendor\rails\ as expected.

I do, however, get error messages when trying to start webrick (error
messages included below).

Am I correct in using tag rel_1-2-2?
Is it the same code as the latest release 1.2.2?
If so, why am I getting error messages?

Thanks for any help,
GiantCranes


---
Error Messages when starting webrick:
---

ruby script/server
 Booting WEBrick...
script/../config/../vendor/rails/activesupport/lib/active_support/de
b:266:in `load_missing_constant': uninitialized constant ActionMaile
)
      from ./script/../config/../vendor/rails/activesupport/lib/acti
ependencies.rb:452:in `const_missing'
      from ./script/../config/../vendor/rails/activesupport/lib/acti
ependencies.rb:464:in `const_missing'
      from ./script/../config/../config/environment.rb:45
      from ./script/../config/../vendor/rails/railties/lib/initializ
`run'
      from ./script/../config/../config/environment.rb:14
      from P:/Program Files/Ruby/lib/ruby/site_ruby/1.8/rubygems/cus
rb:27:in `gem_original_require'
      from P:/Program Files/Ruby/lib/ruby/site_ruby/1.8/rubygems/cus
rb:27:in `require'
      from ./script/../config/../vendor/rails/activesupport/lib/acti
ependencies.rb:495:in `require'
       ... 8 levels...
      from ./script/../config/../vendor/rails/railties/lib/commands/

      from P:/Program Files/Ruby/lib/ruby/site_ruby/1.8/rubygems/cus
rb:27:in `gem_original_require'
      from P:/Program Files/Ruby/lib/ruby/site_ruby/1.8/rubygems/cus
rb:27:in `require'
      from script/server:3
72eb65fa089082d3bd8b38a5596ad331?d=identicon&s=25 Keynan Pratt (keynan)
on 2007-02-08 18:29
Not sure but I would bet that your problem is that you installed your
scripts (script/server) using gem and now it cant find that vender
files.

Hope this helps
82c59780911721f5cbe82d3111313519?d=identicon&s=25 Giant Cranes (giantcranes)
on 2007-02-08 18:30
Keynan Pratt wrote:
> Not sure but I would bet that your problem is that you installed your
> scripts (script/server) using gem and now it cant find that vender
> files.
>
> Hope this helps

If that is the problem, how would I address it?
82c59780911721f5cbe82d3111313519?d=identicon&s=25 Giant Cranes (giantcranes)
on 2007-02-08 18:53
I have narrowed it down to the ActionMailer config:

 ActionMailer::Base.server_settings = {
  :address  => 'mail.server.com',
  :port  => 25,
  :domain  => 'www.server.com',
  :user_name  => 'main@server.com',
  :password  => 'password',
  :authentication  => :login
}

When I comment this out, the application starts successfully. I am
unsure why this  is causing an error, but I will post again here if I do
find out for completeness.

Thanks for your help
2539366e66188d8c5495b187263752b8?d=identicon&s=25 Steve Quezadas (steveeq1)
on 2007-02-28 07:50
(Received via mailing list)
This can be solved by changing:
>  ActionMailer::Base.server_settings = {
>   :address => 'mail.server.com',
>   :port  => 25,
>   :domain => 'www.server.com',
>   :user_name  => '...@server.com',
>   :password  => 'password',
>   :authentication => :login
> }

- to -

>  config.action_mailer.server_settings.server_settings = {
>   :address => 'mail.server.com',
>   :port  => 25,
>   :domain => 'www.server.com',
>   :user_name  => '...@server.com',
>   :password  => 'password',
>   :authentication => :login
> }


On Feb 8, 9:53 am, Giant Cranes <rails-mailing-l...@andreas-s.net>
This topic is locked and can not be replied to.