Edgewall Software

Changes between Version 98 and Version 99 of TracNotification


Ignore:
Timestamp:
Apr 9, 2017, 6:16:49 AM (7 years ago)
Author:
Ryan J Ollos
Comment:

Minor edits.

Legend:

Unmodified
Added
Removed
Modified

  • TracNotification

    v98 v99  
    3030== Configuring SMTP Notification
    3131
    32 '''Important:''' For TracNotification to work correctly, the [[TracIni#trac-base_url-option|[trac] base_url]] option must be configured.
     32'''Important:''' The [[TracIni#trac-base_url-option|[trac] base_url]] option must be configured for links in the notification message to be correctly generated.
    3333
    3434=== Configuration Options
    … …  
    109109 * `prefix`: The prefix defined in `smtp_subject_prefix`.
    110110 * `summary`: The ticket summary, with the old value if the summary was edited.
    111  * `ticket`: The ticket model object (see [trac:source:/trunk/trac/ticket/model.py model.py]). Individual ticket fields can be addressed by appending the field name separated by a dot, eg `${ticket.milestone}`.
     111 * `ticket`: The ticket model object (see [trac:source:/trunk/trac/ticket/model.py model.py]). Individual ticket fields can be accessed by appending the field name separated by a dot, eg `${ticket.milestone}`.
    112112
    113113=== Customizing the e-mail content
    … …  
    196196== Troubleshooting
    197197
    198 If you cannot get the notification working inspect the [TracLogging log] for error messages.
     198If notifications are not working, inspect the [TracLogging log] for error messages.
    199199
    200200Notification errors are not always reported through the web interface, so the user who submits a change or creates a ticket may not get notified about a notification failure. The Trac administrator needs to look at the log to find the error message and traceback.