Yeah, after I updated the plugin it works fine.
On Apr 16, 7:39 am, Dan Croak wrote:
> This should have been fixed in this
> commit:http://github.com/thoughtbot/hoptoad_notifier/commit/da5bc5a09f0d887e...
>
> Thanks,
> Dan
>
>
>
> On Mon, Apr 13, 2009 at 3:47 AM, Ryan Tomayko wrote:
>
> > On S
This should have been fixed in this commit:
http://github.com/thoughtbot/hoptoad_notifier/commit/da5bc5a09f0d887e114e2d3aa86268330e05e513
Thanks,
Dan
On Mon, Apr 13, 2009 at 3:47 AM, Ryan Tomayko wrote:
>
> On Sun, Apr 12, 2009 at 8:44 PM, shenry wrote:
> >
> > I have this same problem, Hoptoa
This is the response I got from hoptoad when I posted the same problem there
-- Forwarded message --
From: Hoptoad Support
Date: Wed, Mar 18, 2009 at 5:18 PM
Subject: Re: errors not reported, seeing standard rails error page
[Problems]
To: yuric...@gmail.com
// Add your reply ab
> There's an open bug in the hoptoad plugin. Full detail below but the
> quick workaround is to add "async." to the "environment_filters" in
> config/initializers/hoptoad.rb as follows:
>
> HoptoadNotifier.configure do |config|
> config.api_key = 'YOUR KEY'
> config.environment_fi
On Sun, Apr 12, 2009 at 8:44 PM, shenry wrote:
>
> I have this same problem, Hoptoad will correctly send a message after
> "heroku rake hoptoad:test" but if I create an exception manually I get
> nothing
>
> Hoptoad Success: Net::HTTPOK
> Rendering /disk1/home/slugs/2185_8e050c1_3bb1/mnt/publ
I have this same problem, Hoptoad will correctly send a message after
"heroku rake hoptoad:test" but if I create an exception manually I get
nothing
Hoptoad Success: Net::HTTPOK
Rendering /disk1/home/slugs/2185_8e050c1_3bb1/mnt/public/500.html (500
Internal Server Error)
Any ideas?
Stu
--~-
I was seeing this at doinlists and now I'm seeing it on another project.
I installed hoptoad, I did the rake test and it successfully sent a message
to hoptoad. Then I pushed to heroku and did "heroku rake hoptoad:test" and
it again successfully sent to hoptoad, this time with a "production"
envi
