-
Notifications
You must be signed in to change notification settings - Fork 415
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
custom section partials not found in view path #10
Comments
I ran across this as well. Thanks for that link. Here is user Nel's excellent fix: Just add to your initializer
|
I ran into this as well - should be fixed asap :) |
As per the README, "you need to inform the gem where the views are. Create an initializer called config/initializers/exception_notifier.rb with the following code: This is the best way to do it. When the application loads the lookup_context isn't available yet, and prepending the view path on every request is out of the question. So it makes sense that in the special cases you need this, you have to add the initializer. Patches are welcome if there's another solution to this I'm not seeing. |
This commit should help in fixing this issue, please test it to see if we can close this issue for good. Thanks! |
@smartinez87 Works great for me using rails.3.1.0.rc5, thanks! Please release a new gem soon :) |
@pdobb, are we ok to close this issue then? |
Yes, and thanks for the help and the nice solution! |
This guy explains the issue nicely: http://stackoverflow.com/questions/5389754/custom-partials-in-exception-notification-in-rails-3
But basically, the view path for the gem seems to be specific to the gem's location and does not consult the app's view path. Is there any help for this or am I just doing it wrong perhaps?
I tried adding a section called
highlights
tooptions[:sections]
and started receiving the error:Thanks
The text was updated successfully, but these errors were encountered: