Exception Notifier seems to have ceased working for some reason. I
thought perhaps a change in edge rails was to blame, but I rolled back
to 4900 and the problem was still there.
The problem is that it generates an error in the _session.rhtml partial.
It looks as if a method in the PP class is bombing. It says wrong
number of argument (1 for 0), but there is no method on that line with
only 1 argument.
Any help is appreciated.
---
ActionView::TemplateError (wrong number of arguments (1 for 0)) on line
#3 of
vendor/plugins/exception_notification/views/exception_notifier/_session.rhtml:
1: <% for variable in @request.session.instance_variables -%>
2: <% next if variable =~ /^@db/ -%>
3: * <%= variable %>: <%=
PP.pp(@request.session.instance_variable_get(variable),"").gsub(/\n/,
"\n ").strip %>
4: <% end -%>
/usr/local/lib/ruby/1.8/pp.rb:244:in `method''
/usr/local/lib/ruby/1.8/pp.rb:244:in `pretty_print''
/usr/local/lib/ruby/1.8/pp.rb:126:in `pp''
...snipped...
---
--
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
-~----------~----~----~----~------~----~------~--~---
Alex Wayne wrote:> Exception Notifier seems to have ceased working for some reason. The > problem is that it generates an error in the _session.rhtml partial. > > --- > ActionView::TemplateError (wrong number of arguments (1 for 0)) on line > #3 of > vendor/plugins/exception_notification/views/exception_notifier/_session.rhtml: > 3: * <%= variable %>: <%= > PP.pp(@request.session.instance_variable_get(variable),"").gsub(/\n/, > "\n ").strip %> > /usr/local/lib/ruby/1.8/pp.rb:244:in `method'' > /usr/local/lib/ruby/1.8/pp.rb:244:in `pretty_print'' > /usr/local/lib/ruby/1.8/pp.rb:126:in `pp'' > ...snipped... > ---bump for great justice. -- 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 -~----------~----~----~----~------~----~------~--~---
I had this problem on edge, but when I backed off to the most recent stable version it went away. Did you way what version of Rails you were running? On Oct 6, 2006, at 9:44 AM, Alex Wayne wrote:> > Alex Wayne wrote: >> Exception Notifier seems to have ceased working for some reason. The >> problem is that it generates an error in the _session.rhtml partial. >> >> --- >> ActionView::TemplateError (wrong number of arguments (1 for 0)) on >> line >> #3 of >> vendor/plugins/exception_notification/views/exception_notifier/ >> _session.rhtml: >> 3: * <%= variable %>: <%>> PP.pp(@request.session.instance_variable_get(variable),"").gsub(/\n/, >> "\n ").strip %> >> /usr/local/lib/ruby/1.8/pp.rb:244:in `method'' >> /usr/local/lib/ruby/1.8/pp.rb:244:in `pretty_print'' >> /usr/local/lib/ruby/1.8/pp.rb:126:in `pp'' >> ...snipped... >> --- > > bump for great justice. > > -- > 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 -~----------~----~----~----~------~----~------~--~---
Steve Ross wrote:> I had this problem on edge, but when I backed off to the most recent > stable version it went away. Did you way what version of Rails you > were running?It seems to be fixed in the latest version of edge. Strange though as I rolled back to 4900 and still had the problem. Perhaps it''s been broken in edge for while? Well it seems ok now. I''ll keep my fingers crossed. -- 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 -~----------~----~----~----~------~----~------~--~---