Unable to find custom section? about exception_notification

[smartinez87]

That's how it's supposed to work. Custom partials should be under app/views/exception_notifier directory, as it explains on the "Customization" part of the README.

Please, correct me if I'm not understanding your issue.

[scrozier]

My custom partial is in app/views/exception_notifier. The problem is that exception_notifier doesn't seem to find it unless I make the change shown in my message. (See the 2nd and 3rd lines of my code.)

So it looks like exception_notifier is doing render 'user', which doesn't have the /exception_notifier/ part of the path.

Maybe it would have been clearer if I had written

summary = render("exception_notifier/#{section}")

above.

Said more succinctly, exception_notifier does not find my custom partial, which is in the right place, as written. I had to modify it (exception_notifier) to find my partial.

Am I making any sense?

[bostrom]

You need to add the path manually e.g. in your initializer file (config/initializers/exception_notifier.rb), like

ExceptionNotifier::Notifier.prepend_view_path File.join(Rails.root, 'app/views')

Maybe this could be done internally, since the documentation instructs to just add views to your /app/views and nothing else?

[scrozier]

Thanks, bostrom...so I'm not crazy.

I'll see if I can't change this in the code and submit a pull request.

[smartinez87]

hey @scrozier @bostrom, is this fixed already? Can I close this issue?

[bostrom]

Not to my knowledge. I haven't checked the code, but at the time of my last comment it didn't work the way the documentation said. So IMO either add the 'app/views' path by default in the code or update the documentation to instruct users to add it manually like I did in my previous comment.

[scrozier]

@smartinez87, no, I don't think it's fixed. I was waiting for some feedback from you, but I think @bostrom and I are in agreement that it's still broken.

I will get on this and submit a pull request today or tomorrow.

[scrozier]

Just submitted a pull request.

Thanks to @bostrom for a clean solution. I was taking a somewhat less elegant approach. :-)

[smartinez87]

pull request #50 fixes this issue, so I'm closing this.