Already initialized constant OPTIONS help please!

=> Booting WEBrick...
c:/RUBY186-25/lib/ruby/gems/1.8/gems/rails-1.2.3/lib/commands/servers/webrick.rb:11:
warning: already initialized constant OPTIONS
=> Booting WEBrick...
c:/RUBY186-25/lib/ruby/gems/1.8/gems/rails-1.2.3/lib/commands/servers/webrick.rb:11:
warning: already initialized constant OPTIONS
c:/RUBY186-25/lib/ruby/gems/1.8/gems/activesupport-1.4.2/lib/active_support/dependencies.rb:249:in
`
load_missing_constant': Expected
./script/../config/../vendor/plugins/acts_as_attachment/lib/technow
eenie/acts_as_attachment.rb to define Technoweenie::ActsAsAttachment
(LoadError)
        from
c:/RUBY186-25/lib/ruby/gems/1.8/gems/activesupport-1.4.2/lib/active_support/dependencie
s.rb:452:in `const_missing'
        from
./script/../config/../vendor/plugins/acts_as_attachment/init.rb:6:in
`load_plugin'
        from
c:/RUBY186-25/lib/ruby/gems/1.8/gems/rails-1.2.3/lib/initializer.rb:401:in
`load_plugin
'
        from
c:/RUBY186-25/lib/ruby/gems/1.8/gems/activesupport-1.4.2/lib/active_support/core_ext/ke
rnel/reporting.rb:11:in `silence_warnings'
        from
c:/RUBY186-25/lib/ruby/gems/1.8/gems/rails-1.2.3/lib/initializer.rb:401:in
`load_plugin
'
        from
c:/RUBY186-25/lib/ruby/gems/1.8/gems/rails-1.2.3/lib/initializer.rb:185:in
`load_plugin
s'
        from
c:/RUBY186-25/lib/ruby/gems/1.8/gems/rails-1.2.3/lib/initializer.rb:185:in
`each'
        from
c:/RUBY186-25/lib/ruby/gems/1.8/gems/rails-1.2.3/lib/initializer.rb:185:in
`load_plugin
s'
         ... 15 levels...
        from
c:/RUBY186-25/lib/ruby/gems/1.8/gems/rails-1.2.3/lib/commands/server.rb:39
        from
c:/RUBY186-25/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:32:in
`gem_original_req
uire'
        from
c:/RUBY186-25/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:32:in
`require'
        from script/server:3

Not real sure what to do about this error when trying to run webrick. I
have uninstalled reinstalled ruby, updated gems, updated rails... all
updates, installs went good yet this error still occurs.

···

--
Posted via http://www.ruby-forum.com/.

Your real problem is:
c:/RUBY186-25/lib/ruby/gems/1.8/gems/activesupport-1.4.2
/lib/active_support/dependencies.rb:249:in
`
load_missing_constant': Expected
./script/../config/../vendor/plugins/acts_as_attachment/lib/technow
eenie/acts_as_attachment.rb to define Technoweenie::ActsAsAttachment
(LoadError)

I'm not sure exactly under what circumstances rails raises what exceptions,
but the LoadError seems to indicate that the file acts_as_attachment.rb in
the directory technoweenie is missing. Furthermore it seems to expect it to
be in the plugins dir of your rails project
(vendor/plugins/acts_as_attachment/lib/technoweenie/acts_as_attachment.rb).
If that file is missing I think you've found your culprit.

···

On 7/5/07, DM <double_helix_studios@hotmail.com> wrote:

=> Booting WEBrick...
c:/RUBY186-25/lib/ruby/gems/1.8/gems/rails-1.2.3
/lib/commands/servers/webrick.rb:11:
warning: already initialized constant OPTIONS
=> Booting WEBrick...
c:/RUBY186-25/lib/ruby/gems/1.8/gems/rails-1.2.3
/lib/commands/servers/webrick.rb:11:
warning: already initialized constant OPTIONS
c:/RUBY186-25/lib/ruby/gems/1.8/gems/activesupport-1.4.2
/lib/active_support/dependencies.rb:249:in
`
load_missing_constant': Expected
./script/../config/../vendor/plugins/acts_as_attachment/lib/technow
eenie/acts_as_attachment.rb to define Technoweenie::ActsAsAttachment
(LoadError)
        from
c:/RUBY186-25/lib/ruby/gems/1.8/gems/activesupport-1.4.2
/lib/active_support/dependencie
s.rb:452:in `const_missing'
        from
./script/../config/../vendor/plugins/acts_as_attachment/init.rb:6:in
`load_plugin'
        from
c:/RUBY186-25/lib/ruby/gems/1.8/gems/rails-1.2.3/lib/initializer.rb:401:in
`load_plugin
'
        from
c:/RUBY186-25/lib/ruby/gems/1.8/gems/activesupport-1.4.2
/lib/active_support/core_ext/ke
rnel/reporting.rb:11:in `silence_warnings'
        from
c:/RUBY186-25/lib/ruby/gems/1.8/gems/rails-1.2.3/lib/initializer.rb:401:in
`load_plugin
'
        from
c:/RUBY186-25/lib/ruby/gems/1.8/gems/rails-1.2.3/lib/initializer.rb:185:in
`load_plugin
s'
        from
c:/RUBY186-25/lib/ruby/gems/1.8/gems/rails-1.2.3/lib/initializer.rb:185:in
`each'
        from
c:/RUBY186-25/lib/ruby/gems/1.8/gems/rails-1.2.3/lib/initializer.rb:185:in
`load_plugin
s'
         ... 15 levels...
        from
c:/RUBY186-25/lib/ruby/gems/1.8/gems/rails-1.2.3/lib/commands/server.rb:39
        from
c:/RUBY186-25/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:32:in
`gem_original_req
uire'
        from
c:/RUBY186-25/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:32:in
`require'
        from script/server:3

Not real sure what to do about this error when trying to run webrick. I
have uninstalled reinstalled ruby, updated gems, updated rails... all
updates, installs went good yet this error still occurs.

--
Posted via http://www.ruby-forum.com/\.

Already initialized constant OPTIONS is a red-herring, it's a warning.

I'm not sure exactly under what circumstances rails raises what
exceptions,
but the LoadError seems to indicate that the file acts_as_attachment.rb
in
the directory technoweenie is missing. Furthermore it seems to expect it
to
be in the plugins dir of your rails project
(vendor/plugins/acts_as_attachment/lib/technoweenie/acts_as_attachment.rb).
If that file is missing I think you've found your culprit.

I really wish the problem was this easy. I do have that plugin and path
in my rails application.

The strange thing I discovered this afternoon was if I was to remove the
acts_as_attachment plugin from my rails app.. then I will get the same
error running ruby script/server pointing its finger at the next
remaining plugin in my list acts_as_paranoid.

So, it would appear that whatever this problem is it has something to do
with linking the way ruby finds my plugins... it is error'ing out on the
first one it comes across.

···

--
Posted via http://www.ruby-forum.com/\.

I would suggest maybe taking this to the rails list. Looks like it is some
sort of issue with how rails's plugin loading works.

···

On 7/5/07, Dan Morton <dan.e.morton@gmail.com> wrote:

> I'm not sure exactly under what circumstances rails raises what
> exceptions,
> but the LoadError seems to indicate that the file acts_as_attachment.rb
> in
> the directory technoweenie is missing. Furthermore it seems to expect it
> to
> be in the plugins dir of your rails project
>
(vendor/plugins/acts_as_attachment/lib/technoweenie/acts_as_attachment.rb).
> If that file is missing I think you've found your culprit.

I really wish the problem was this easy. I do have that plugin and path
in my rails application.

The strange thing I discovered this afternoon was if I was to remove the
acts_as_attachment plugin from my rails app.. then I will get the same
error running ruby script/server pointing its finger at the next
remaining plugin in my list acts_as_paranoid.

So, it would appear that whatever this problem is it has something to do
with linking the way ruby finds my plugins... it is error'ing out on the
first one it comes across.

--

Posted via http://www.ruby-forum.com/\.

Unfortunately, you might want to find a different Rails forum/list than the one set up as a google talk list. It's not too responsive.

···

On Jul 5, 2007, at 4:38 PM, Logan Capaldo wrote:

On 7/5/07, Dan Morton <dan.e.morton@gmail.com> wrote:

> I'm not sure exactly under what circumstances rails raises what
> exceptions,
> but the LoadError seems to indicate that the file acts_as_attachment.rb
> in
> the directory technoweenie is missing. Furthermore it seems to expect it
> to
> be in the plugins dir of your rails project
>
(vendor/plugins/acts_as_attachment/lib/technoweenie/acts_as_attachment.rb).
> If that file is missing I think you've found your culprit.

I really wish the problem was this easy. I do have that plugin and path
in my rails application.

The strange thing I discovered this afternoon was if I was to remove the
acts_as_attachment plugin from my rails app.. then I will get the same
error running ruby script/server pointing its finger at the next
remaining plugin in my list acts_as_paranoid.

So, it would appear that whatever this problem is it has something to do
with linking the way ruby finds my plugins... it is error'ing out on the
first one it comes across.

I would suggest maybe taking this to the rails list. Looks like it is some
sort of issue with how rails's plugin loading works.

--