> When i go to my first view, i get this very weird error:
>
> wrong number of arguments (2 for 0)
That means you're calling some function/method that's expecting no
arguments, and you're giving it two.
> It goes wrong in the callbacks, in the following function:
>
> def run_callbacks(kind, *args, &block)
> send("_run_#{kind}_callbacks", *args, &block)
> end
My guess would be that the callback is expecting no args, but is being
sent *args and &block. Even if it ignores them, it should probably
accept them. Try that and see if it works....
-Dave
--
Specialization is for insects. -RAH | Have Pun, Will Babble! -me
Programming Blog: http://codosaur.us | Work: http://davearonson.com
Leadership Blog: http://dare2xl.com | Play: http://davearonson.net
> But luckily, as is often the case, the problem/bug was a stupid
> mistake.
>
> My class is called EnvelopesController, and what did i want to do with
> my envelopes? send them!
> Alas, defining a such-named method will cause terrible havoc! :D
That's the sort of thing that seems to strike Rails devs all the time.
Happened to me when I named something "options" IIRC. It seems
similar to someone's dictum on gun handling: there are shooters who
have had accidental discharges, and shooters who *will*. :-)
Perhaps there ought to be a gem/plugin/whatever that will warn you if
it detects reuse of a word that Rails uses....