thr3ads.net - Rails - NoMethodError after upgrading from 1.1.6 to 1.2.3 [Dec 2007]

If this information is useful, please help other people find it:
Share via:

Evan

2007-Dec-05 20:06 UTC

NoMethodError after upgrading from 1.1.6 to 1.2.3

After upgrading from Rails 1.1.6 to 1.2.3 I receive a NoMethodError
when loading a particular page in my app (see http://pastie.caboo.se/125097).
Here''s what I know about it:

-The issue occurs in the development environment, but not in the
production environment on the same CPU using the same database under
the same server software/rails installation
-If the troublesome page is loaded directly it loads the first time
and throws the error on subsequent loads
-If the troublesome page is loaded through a link from another page it
throws an error immediately
-The "q" variable does not change between lines 6 and 7
-The page executes to line 6 without error
-No changes have been made to the models, controller or view involved
since upgrading
-The page operated normally in development and production environments
under 1.1.6

What could be causing this problem?

http://pastie.caboo.se/125097
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Frederick Cheung

2007-Dec-05 20:23 UTC

head link

Re: NoMethodError after upgrading from 1.1.6 to 1.2.3

On Dec 5, 8:06 pm, Evan
<evancha...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
wrote:> After upgrading from Rails 1.1.6 to 1.2.3 I receive a NoMethodError
> when loading a particular page in my app
(seehttp://pastie.caboo.se/125097).
> Here''s what I know about it:
>
This sounds like a dependency problem (there were a bunch of changes
to that for rails 1.2). In a nutshell, between requests rails clears
out all your controllers, models etc... and loads fresh ones. If that
goes wrong, then you can end up with something using the old Question
class (the one that rails cleared out) and shit happens. Classes
aren''t reloaded between requests in production, so the problem
doesn''t
exist there.

Reasons i''ve seen this happen
- plugins: by default these are not reloading between requests, so if
a plugin holds onto a class it will get borked
- requiring things ''by hand''. This bypasses the rails autoload
magic
and so it gets confused. Use require_dependency, or let autoloading do
its magic
- doing weird stuff like including a module into the top level
I can''t see any of this in the code you''ve shown, but it
doesn''t
necessarily have to be (eg stuff in your environment.rb could do it,
stuff in the editor model could do it etc...
Hopefully this should point you in the right direction. The
Dependencies stuff can log all the stuff it does, which can be helpful
in tracking down this sort of stuff.

Fred
> -The issue occurs in the development environment, but not in the
> production environment on the same CPU using the same database under
> the same server software/rails installation
> -If the troublesome page is loaded directly it loads the first time
> and throws the error on subsequent loads
> -If the troublesome page is loaded through a link from another page it
> throws an error immediately
> -The "q" variable does not change between lines 6 and 7
> -The page executes to line 6 without error
> -No changes have been made to the models, controller or view involved
> since upgrading
> -The page operated normally in development and production environments
> under 1.1.6
>
> What could be causing this problem?
>
> http://pastie.caboo.se/125097--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Evan

2007-Dec-05 20:30 UTC

head link

Re: NoMethodError after upgrading from 1.1.6 to 1.2.3

Fred,

That does give me some more direction. Thank you. How do I activate
the dependencies logging?

Evan
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Frederick Cheung

2007-Dec-05 20:34 UTC

head link

Re: NoMethodError after upgrading from 1.1.6 to 1.2.3

On 5 Dec 2007, at 20:30, Evan wrote:
>
> Fred,
>
> That does give me some more direction. Thank you. How do I activate
> the dependencies logging?
>
You set Dependencies.log_activity to true. In addition there are  
plenty of good methods in there to pepper with extra logging. Also  
checkout ActiveRecord::Base.reset_subclasses if there is a class there  
that isn''t being unloaded then logging there can pick that up

Fred
> Evan
> >

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Rob Biedenharn

2007-Dec-05 21:02 UTC

head link

Re: NoMethodError after upgrading from 1.1.6 to 1.2.3

On Dec 5, 2007, at 3:06 PM, Evan wrote:> After upgrading from Rails 1.1.6 to 1.2.3 I receive a NoMethodError
> when loading a particular page in my app (see
http://pastie.caboo.se/125097)
> .
> Here''s what I know about it:
>
> -The issue occurs in the development environment, but not in the
> production environment on the same CPU using the same database under
> the same server software/rails installation
> -If the troublesome page is loaded directly it loads the first time
> and throws the error on subsequent loads
> -If the troublesome page is loaded through a link from another page it
> throws an error immediately
> -The "q" variable does not change between lines 6 and 7
> -The page executes to line 6 without error
> -No changes have been made to the models, controller or view involved
> since upgrading
> -The page operated normally in development and production environments
> under 1.1.6
>
> What could be causing this problem?
>
> http://pastie.caboo.se/125097

shouldn''t it be

   has_many :advices
(i.e., plural like the table name, not singular)

-Rob

Rob Biedenharn		http://agileconsultingllc.com
Rob-xa9cJyRlE0mWcWVYNo9pwxS2lgjeYSpx@public.gmane.org



--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Frederick Cheung

2007-Dec-05 21:52 UTC

head link

Re: NoMethodError after upgrading from 1.1.6 to 1.2.3

On 5 Dec 2007, at 21:02, Rob Biedenharn wrote:
>
> On Dec 5, 2007, at 3:06 PM, Evan wrote:
>> After upgrading from Rails 1.1.6 to 1.2.3 I receive a NoMethodError
>> when loading a particular page in my app (see
http://pastie.caboo.se/125097)
>> .
>> Here''s what I know about it:
>>
>> -The issue occurs in the development environment, but not in the
>> production environment on the same CPU using the same database under
>> the same server software/rails installation
>> -If the troublesome page is loaded directly it loads the first time
>> and throws the error on subsequent loads
>> -If the troublesome page is loaded through a link from another page  
>> it
>> throws an error immediately
>> -The "q" variable does not change between lines 6 and 7
>> -The page executes to line 6 without error
>> -No changes have been made to the models, controller or view involved
>> since upgrading
>> -The page operated normally in development and production  
>> environments
>> under 1.1.6
>>
>> What could be causing this problem?
>>
>> http://pastie.caboo.se/125097
>
>
> shouldn''t it be
>
>   has_many :advices
> (i.e., plural like the table name, not singular)
>Arguably bad form, but hardly accounts for it working in production  
and working in development mode the first time.
You can get away with it because ''advice''.singularize ==
''advice''

Fred
> -Rob
>
> Rob Biedenharn		http://agileconsultingllc.com
> Rob-xa9cJyRlE0mWcWVYNo9pwxS2lgjeYSpx@public.gmane.org
>
>
>
> >

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Ryan Bigg

2007-Dec-06 00:26 UTC

head link

Re: NoMethodError after upgrading from 1.1.6 to 1.2.3

I wouldn''t recommend using a word that cannot be pluralised. Try its
synonyms:

http://thesaurus.reference.com/browse/advice

On Dec 6, 2007 8:22 AM, Frederick Cheung
<frederick.cheung-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
>
> On 5 Dec 2007, at 21:02, Rob Biedenharn wrote:
>
> >
> > On Dec 5, 2007, at 3:06 PM, Evan wrote:
> >> After upgrading from Rails 1.1.6 to 1.2.3 I receive a
NoMethodError
> >> when loading a particular page in my app (see
> http://pastie.caboo.se/125097)
> >> .
> >> Here''s what I know about it:
> >>
> >> -The issue occurs in the development environment, but not in the
> >> production environment on the same CPU using the same database
under
> >> the same server software/rails installation
> >> -If the troublesome page is loaded directly it loads the first
time
> >> and throws the error on subsequent loads
> >> -If the troublesome page is loaded through a link from another
page
> >> it
> >> throws an error immediately
> >> -The "q" variable does not change between lines 6 and 7
> >> -The page executes to line 6 without error
> >> -No changes have been made to the models, controller or view
involved
> >> since upgrading
> >> -The page operated normally in development and production
> >> environments
> >> under 1.1.6
> >>
> >> What could be causing this problem?
> >>
> >> http://pastie.caboo.se/125097
> >
> >
> > shouldn''t it be
> >
> >   has_many :advices
> > (i.e., plural like the table name, not singular)
> >
> Arguably bad form, but hardly accounts for it working in production
> and working in development mode the first time.
> You can get away with it because ''advice''.singularize ==
''advice''
>
> Fred
>
> > -Rob
> >
> > Rob Biedenharn                http://agileconsultingllc.com
> > Rob-xa9cJyRlE0mWcWVYNo9pwxS2lgjeYSpx@public.gmane.org
> >
> >
> >
> > >
>
>
> >
>

-- 
Ryan Bigg

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Karthi kn

2007-Dec-06 13:10 UTC

head link

Re: NoMethodError after upgrading from 1.1.6 to 1.2.3

Evan wrote:> After upgrading from Rails 1.1.6 to 1.2.3 I receive a NoMethodError
> when loading a particular page in my app (see 
> http://pastie.caboo.se/125097).
> Here''s what I know about it:
> 
> -The issue occurs in the development environment, but not in the
> production environment on the same CPU using the same database under
> the same server software/rails installation
> -If the troublesome page is loaded directly it loads the first time
> and throws the error on subsequent loads
> -If the troublesome page is loaded through a link from another page it
> throws an error immediately
> -The "q" variable does not change between lines 6 and 7
> -The page executes to line 6 without error
> -No changes have been made to the models, controller or view involved
> since upgrading
> -The page operated normally in development and production environments
> under 1.1.6
> 
> What could be causing this problem?
> 
> http://pastie.caboo.se/125097

Try adding the following statement in question.rb

require ''advice.rb''

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

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

ebrad

2007-Dec-06 14:42 UTC

head link

Re: NoMethodError after upgrading from 1.1.6 to 1.2.3

I agree with Rob.  Seems like the problem is in the naming. I would
try it with the model name ''advices'', or a more
straight-forward word
like ''answers'' or ''suggestions''.  Then, you
can change the view code
to read "<% if q.advices.empty? %>"

good luck

On Dec 5, 3:06 pm, Evan
<evancha...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
wrote:> After upgrading from Rails 1.1.6 to 1.2.3 I receive a NoMethodError
> when loading a particular page in my app
(seehttp://pastie.caboo.se/125097).
> Here''s what I know about it:
>
> -The issue occurs in the development environment, but not in the
> production environment on the same CPU using the same database under
> the same server software/rails installation
> -If the troublesome page is loaded directly it loads the first time
> and throws the error on subsequent loads
> -If the troublesome page is loaded through a link from another page it
> throws an error immediately
> -The "q" variable does not change between lines 6 and 7
> -The page executes to line 6 without error
> -No changes have been made to the models, controller or view involved
> since upgrading
> -The page operated normally in development and production environments
> under 1.1.6
>
> What could be causing this problem?
>
> http://pastie.caboo.se/125097--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Evan

2007-Dec-07 05:37 UTC

head link

Re: NoMethodError after upgrading from 1.1.6 to 1.2.3

Hmmm...I activated dependencies logging, but am not sure what to make
of the logged activity.

http://pastie.caboo.se/125830

On Dec 5, 12:34 pm, Frederick Cheung
<frederick.che...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
wrote:> On 5 Dec 2007, at 20:30, Evan wrote:
>
>
>
> > Fred,
>
> > That does give me some more direction. Thank you. How do I activate
> > the dependencies logging?
>
> You set Dependencies.log_activity to true. In addition there are  
> plenty of good methods in there to pepper with extra logging. Also  
> checkout ActiveRecord::Base.reset_subclasses if there is a class there  
> that isn''t being unloaded then logging there can pick that up
>
> Fred
>
> > Evan--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Evan

2007-Dec-07 05:39 UTC

head link

Re: NoMethodError after upgrading from 1.1.6 to 1.2.3

I have adjusted the plurality of the advice/question association in
the models, controllers and views and the issue persists.

On Dec 5, 1:02 pm, Rob Biedenharn
<R...-xa9cJyRlE0mWcWVYNo9pwxS2lgjeYSpx@public.gmane.org>
wrote:> On Dec 5, 2007, at 3:06 PM, Evan wrote:
>
>
>
> > After upgrading from Rails 1.1.6 to 1.2.3 I receive a NoMethodError
> > when loading a particular page in my app
(seehttp://pastie.caboo.se/125097)
> > .
> > Here''s what I know about it:
>
> > -The issue occurs in the development environment, but not in the
> > production environment on the same CPU using the same database under
> > the same server software/rails installation
> > -If the troublesome page is loaded directly it loads the first time
> > and throws the error on subsequent loads
> > -If the troublesome page is loaded through a link from another page it
> > throws an error immediately
> > -The "q" variable does not change between lines 6 and 7
> > -The page executes to line 6 without error
> > -No changes have been made to the models, controller or view involved
> > since upgrading
> > -The page operated normally in development and production environments
> > under 1.1.6
>
> > What could be causing this problem?
>
> >http://pastie.caboo.se/125097
>
> shouldn''t it be
>
>    has_many :advices
> (i.e., plural like the table name, not singular)
>
> -Rob
>
> Rob Biedenharn          http://agileconsultingllc.com
> R...-xa9cJyRlE0mWcWVYNo9pwxS2lgjeYSpx@public.gmane.org--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Evan

2007-Dec-07 05:40 UTC

head link

Re: NoMethodError after upgrading from 1.1.6 to 1.2.3

I have tried adding "require ''advice.rb''" to the
Question class
definition and the issue persists.

On Dec 6, 5:10 am, Karthi kn
<rails-mailing-l...-ARtvInVfO7ksV2N9l4h3zg@public.gmane.org>
wrote:> Evan wrote:
> > After upgrading from Rails 1.1.6 to 1.2.3 I receive a NoMethodError
> > when loading a particular page in my app (see
> >http://pastie.caboo.se/125097).
> > Here''s what I know about it:
>
> > -The issue occurs in the development environment, but not in the
> > production environment on the same CPU using the same database under
> > the same server software/rails installation
> > -If the troublesome page is loaded directly it loads the first time
> > and throws the error on subsequent loads
> > -If the troublesome page is loaded through a link from another page it
> > throws an error immediately
> > -The "q" variable does not change between lines 6 and 7
> > -The page executes to line 6 without error
> > -No changes have been made to the models, controller or view involved
> > since upgrading
> > -The page operated normally in development and production environments
> > under 1.1.6
>
> > What could be causing this problem?
>
> >http://pastie.caboo.se/125097
>
> Try adding the following statement in question.rb
>
> require ''advice.rb''
>
> --
> Posted viahttp://www.ruby-forum.com/.--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Frederick Cheung

2007-Dec-07 08:29 UTC

head link

Re: NoMethodError after upgrading from 1.1.6 to 1.2.3

On 7 Dec 2007, at 05:40, Evan wrote:
>
> I have tried adding "require ''advice.rb''" to
the Question class
> definition and the issue persists.
>
Are you sticking an entire editor object in the session? Does changing  
that fix things?

Fred> On Dec 6, 5:10 am, Karthi kn
<rails-mailing-l...-ARtvInVfO7ksV2N9l4h3zg@public.gmane.org> wrote:
>> Evan wrote:
>>> After upgrading from Rails 1.1.6 to 1.2.3 I receive a NoMethodError
>>> when loading a particular page in my app (see
>>> http://pastie.caboo.se/125097).
>>> Here''s what I know about it:
>>
>>> -The issue occurs in the development environment, but not in the
>>> production environment on the same CPU using the same database
under
>>> the same server software/rails installation
>>> -If the troublesome page is loaded directly it loads the first time
>>> and throws the error on subsequent loads
>>> -If the troublesome page is loaded through a link from another  
>>> page it
>>> throws an error immediately
>>> -The "q" variable does not change between lines 6 and 7
>>> -The page executes to line 6 without error
>>> -No changes have been made to the models, controller or view  
>>> involved
>>> since upgrading
>>> -The page operated normally in development and production  
>>> environments
>>> under 1.1.6
>>
>>> What could be causing this problem?
>>
>>> http://pastie.caboo.se/125097
>>
>> Try adding the following statement in question.rb
>>
>> require ''advice.rb''
>>
>> --
>> Posted viahttp://www.ruby-forum.com/.
> >

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Frederick Cheung

2007-Dec-07 08:46 UTC

head link

Re: NoMethodError after upgrading from 1.1.6 to 1.2.3

On 7 Dec 2007, at 05:37, Evan wrote:
>
> Hmmm...I activated dependencies logging, but am not sure what to make
> of the logged activity.
>
> http://pastie.caboo.se/125830
>
Well you can sort of see what is happening, if you compare the good  
load with the bad load:

Good:

Processing EditingController#index (for 127.0.0.1 at 2007-12-06  
21:11:01)
[GET] Session ID: bd965b771927a6b290bbdc5018fe0364
Parameters: {"action"=>"index",
"controller"=>"editing"}
DEPRECATION WARNING: @session is deprecated! Call session.[] instead  
of @session.[]. Args: ["editor"] See
http://www.rubyonrails.org/deprecation
  for details. (called from editor? at /Users/evan/Rails/asktheguys/ 
asktheguys/public/../config/../lib/editor_system.rb:87)
DEPRECATION WARNING: @session is deprecated! Call session.[] instead  
of @session.[]. Args: ["editor"] See
http://www.rubyonrails.org/deprecation
  for details. (called from login_required at /Users/evan/Rails/ 
asktheguys/asktheguys/public/../config/../lib/editor_system.rb:47)
Dependencies: called load_missing_constant(Object, :Question)  
Dependencies: called require_or_load("/Users/evan/Rails/asktheguys/ 
asktheguys/public/../config/../app/models/question.rb", nil)  
Dependencies: loading /Users/evan/Rails/asktheguys/asktheguys/ 
public/../config/../app/models/question Dependencies: called  
load_file("/Users/evan/Rails/asktheguys/asktheguys/public/../config/../ 
app/models/question.rb", ["Models::Question",
"Question"])
Dependencies: called new_constants_in("Models", :Object)
Dependencies: New constants: Question Dependencies: loading /Users/ 
evan/Rails/asktheguys/asktheguys/public/../config/../app/models/ 
question.rb defined Question
Question  [4;36;1mQuestion Columns (0.000593) [0m  [0;1mSHOW FIELDS  
FROM questions [0m  [4;35;1mSQL (0.000748) [0m  [0mSELECT count(*) AS  
count_all FROM questions  [0m  [4;36;1mQuestion Load (0.000936) [0m  
 [0;1mSELECT * FROM questions ORDER BY questions.created_on DESC LIMIT  
0, 10 [0m

Bad:

Processing EditingController#index (for 127.0.0.1 at 2007-12-06  
21:11:09)
[GET] Session ID: bd965b771927a6b290bbdc5018fe0364 Parameters:  
{"action"=>"index",
"controller"=>"editing"}
DEPRECATION WARNING: @session is deprecated! Call session.[] instead  
of @session.[]. Args: ["editor"] See
http://www.rubyonrails.org/deprecation
  for details. (called from editor? at /Users/evan/Rails/asktheguys/ 
asktheguys/public/../config/../lib/editor_system.rb:87)
DEPRECATION WARNING: @session is deprecated! Call session.[] instead  
of @session.[]. Args: ["editor"] See
http://www.rubyonrails.org/deprecation
  for details. (called from login_required at /Users/evan/Rails/ 
asktheguys/asktheguys/public/../config/../lib/editor_system.rb:47)  
[4;36;1mQuestion Columns (0.001567) [0m  [0;1mSHOW FIELDS FROM  
questions [0m  [4;35;1mSQL (0.000583) [0m  [0mSELECT count(*) AS  
count_all FROM questions  [0m  [4;36;1mQuestion Load (0.000810) [0m  
 [0;1mSELECT * FROM questions ORDER BY questions.created_on DESC LIMIT  
0, 10 [0m
See how in the first case Question is loaded from question.rb, but not  
in the second case -> something is hanging on to a stale reference to  
the question class, and it''s something that happens in  
editor_system.rb (like i said in my other mail, if you''re putting an  
editor object in the session, that''s bad)

Fred> On Dec 5, 12:34 pm, Frederick Cheung
<frederick.che...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> wrote:
>> On 5 Dec 2007, at 20:30, Evan wrote:
>>
>>
>>
>>> Fred,
>>
>>> That does give me some more direction. Thank you. How do I activate
>>> the dependencies logging?
>>
>> You set Dependencies.log_activity to true. In addition there are
>> plenty of good methods in there to pepper with extra logging. Also
>> checkout ActiveRecord::Base.reset_subclasses if there is a class  
>> there
>> that isn''t being unloaded then logging there can pick that up
>>
>> Fred
>>
>>> Evan
> >

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Rails - Dec 2007 - NoMethodError after upgrading from 1.1.6 to 1.2.3

NoMethodError after upgrading from 1.1.6 to 1.2.3

Re: NoMethodError after upgrading from 1.1.6 to 1.2.3

Re: NoMethodError after upgrading from 1.1.6 to 1.2.3

Re: NoMethodError after upgrading from 1.1.6 to 1.2.3

Re: NoMethodError after upgrading from 1.1.6 to 1.2.3

Re: NoMethodError after upgrading from 1.1.6 to 1.2.3

Re: NoMethodError after upgrading from 1.1.6 to 1.2.3

Re: NoMethodError after upgrading from 1.1.6 to 1.2.3

Re: NoMethodError after upgrading from 1.1.6 to 1.2.3

Re: NoMethodError after upgrading from 1.1.6 to 1.2.3

Re: NoMethodError after upgrading from 1.1.6 to 1.2.3

Re: NoMethodError after upgrading from 1.1.6 to 1.2.3

Re: NoMethodError after upgrading from 1.1.6 to 1.2.3

Re: NoMethodError after upgrading from 1.1.6 to 1.2.3