forked from smartinez87/exception_notification
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request smartinez87#18 from professor/master
Clarified how to customize or add a new view
- Loading branch information
Showing
1 changed file
with
15 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -49,8 +49,21 @@ access to the following variables: | |
You can reorder the sections, or exclude sections completely, by altering the | ||
ExceptionNotifier.sections variable. You can even add new sections that | ||
describe application-specific data--just add the section's name to the list | ||
(whereever you'd like), and define the corresponding partial. Then, if your | ||
new section requires information that isn't available by default, make sure | ||
(wherever you'd like), and define the corresponding partial. | ||
|
||
#Example with two new added sections | ||
Whatever::Application.config.middleware.use ExceptionNotifier, | ||
:email_prefix => "[Whatever] ", | ||
:sender_address => %{"notifier" <[email protected]>}, | ||
:exception_recipients => %w{[email protected]}, | ||
:sections => %w{my_section1 my_section2} + ExceptionNotifier::Notifier.default_sections | ||
|
||
When you add a new section or customize a section, you need to inform the gem where the views are. | ||
Create an initializer called config/initializers/exception_notifier.rb with the following code: | ||
|
||
ExceptionNotifier::Notifier.prepend_view_path File.join(Rails.root, 'app/views') | ||
|
||
If your new section requires information that isn't available by default, make sure | ||
it is made available to the email using the exception_data macro: | ||
|
||
class ApplicationController < ActionController::Base | ||
|