Mercurial > p > roundup > code

comparison doc/customizing.txt @ 2121:fd5459469069

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Did a couple of things: o- Did the proper doc thing, under Richard's stern disciplinary action - Updated Changes.txt - Updated Customizing doc - Took a change out of upgrading.txt that didn't need to be there - Made config.py be the same as the minimal config.py
author Eddie Parker <eparker@users.sourceforge.net>
date Thu, 25 Mar 2004 22:38:55 +0000
parents 90769be53b4b
children 7109f83d5250
comparison
equal deleted inserted replaced
2120:09ad4c25fca1 2121:fd5459469069
1 =================== 1 ===================
2 Customising Roundup 2 Customising Roundup
3 =================== 3 ===================
4 4
5 :Version: $Revision: 1.120 $ 5 :Version: $Revision: 1.121 $
6 6
7 .. This document borrows from the ZopeBook section on ZPT. The original is at: 7 .. This document borrows from the ZopeBook section on ZPT. The original is at:
8 http://www.zope.org/Documentation/Books/ZopeBook/current/ZPT.stx 8 http://www.zope.org/Documentation/Books/ZopeBook/current/ZPT.stx
9 9
10 .. contents:: 10 .. contents::
133 the tracker. You **must** include a trailing '/' in the URL. 133 the tracker. You **must** include a trailing '/' in the URL.
134 134
135 **ADMIN_EMAIL** - ``'roundup-admin@%s'%MAIL_DOMAIN`` 135 **ADMIN_EMAIL** - ``'roundup-admin@%s'%MAIL_DOMAIN``
136 The email address that roundup will complain to if it runs into trouble. 136 The email address that roundup will complain to if it runs into trouble.
137 137
138 **DISPATCHER_EMAIL** - ``ADMIN_EMAIL``
139 The email address that roundup will issue all error messages to. This is
140 also useful, if you want to switch your 'new message' notification to
141 a central user.
142
138 **EMAIL_FROM_TAG** - ``''`` 143 **EMAIL_FROM_TAG** - ``''``
139 Additional text to include in the "name" part of the ``From:`` address used 144 Additional text to include in the "name" part of the ``From:`` address used
140 in nosy messages. If the sending user is "Foo Bar", the ``From:`` line is 145 in nosy messages. If the sending user is "Foo Bar", the ``From:`` line is
141 usually:: 146 usually::
142 147
143 "Foo Bar" <issue_tracker@tracker.example> 148 "Foo Bar" <issue_tracker@tracker.example>
144 149
145 The EMAIL_FROM_TAG goes inside the "Foo Bar" quotes like so:: 150 The EMAIL_FROM_TAG goes inside the "Foo Bar" quotes like so::
146 151
147 "Foo Bar EMAIL_FROM_TAG" <issue_tracker@tracker.example> 152 "Foo Bar EMAIL_FROM_TAG" <issue_tracker@tracker.example>
153
154 **ERROR_MESSAGES_TO** - ``'user'``, ``'dispatcher'`` or ``'both'``
155 Sends error messages to the dispatcher, user, or both.
148 156
149 **MESSAGES_TO_AUTHOR** - ``'new'``, ``'yes'`` or``'no'`` 157 **MESSAGES_TO_AUTHOR** - ``'new'``, ``'yes'`` or``'no'``
150 Send nosy messages to the author of the message? 158 Send nosy messages to the author of the message?
151 If 'new' is used, then the author will only be sent the message when the 159 If 'new' is used, then the author will only be sent the message when the
152 message creates a new issue. If 'yes' then the author will always be sent 160 message creates a new issue. If 'yes' then the author will always be sent
2809 . 2817 .
2810 . 2818 .
2811 </form> 2819 </form>
2812 2820
2813 Note that later in the form, I test the value of "cat" include form 2821 Note that later in the form, I test the value of "cat" include form
2814 elements that are appropriate. For exsample:: 2822 elements that are appropriate. For example::
2815 2823
2816 <tal:block tal:condition="python:cat in '6 10 13 14 15 16 17'.split()"> 2824 <tal:block tal:condition="python:cat in '6 10 13 14 15 16 17'.split()">
2817 <tr> 2825 <tr>
2818 <th>Operating System</th> 2826 <th>Operating System</th>
2819 <td tal:content="structure context/os/field"></td> 2827 <td tal:content="structure context/os/field"></td>
Roundup Issue Tracker: http://roundup-tracker.org/