|
1 | | -2002-02-05 eg |
| 1 | +Roundup FAQ |
2 | 2 |
|
3 | | -NOTE: This is just a grabbag, most of this should go into |
4 | | - documentation. |
| 3 | + '$Date: 2002-02-14 08:50:14 $' |
| 4 | + |
| 5 | + NOTE: This is just a grabbag, most of this should go into documentation. |
5 | 6 |
|
6 | 7 | Changing HTML layout |
7 | 8 |
|
8 | 9 | Note changes to the files in html take place immediatly without |
9 | 10 | restart, even when running roundup-server. |
10 | 11 |
|
| 12 | + Displaying whole messages not only the summary |
| 13 | + |
| 14 | + Modify instance/html/msg.index change:: |
| 15 | + |
| 16 | + <td><display call="plain('summary')"></td> |
| 17 | + |
| 18 | + to:: |
| 19 | + |
| 20 | + <td><pre><display call="plain('content')"></pre></td> |
| 21 | + |
| 22 | + displays the whole message not only the first line and 'pre' |
| 23 | + prevents the browser from reformatting. |
| 24 | + |
| 25 | + Getting the nosy list picker instead of textfield. |
| 26 | + |
| 27 | + In classic template there is plenty of space below the text field. |
| 28 | + So one could modify instance/html/issue.item to use it. |
| 29 | + |
| 30 | + At the file top set 'border=1' to see cell boundaries, then |
| 31 | + replace:: |
| 32 | + |
| 33 | + <td class="form-text"><display call="field('nosy',size=20)"></td> |
| 34 | + |
| 35 | + by:: |
| 36 | + |
| 37 | + <td rowspan=5 class="form-text"><display call="menu('nosy',height=10)"></td> |
| 38 | + |
| 39 | + and remove the last cell in the next four rows, either by deleting a cell |
| 40 | + or by reducing colspan. |
| 41 | + |
| 42 | + Want to see the issue id (the number) on the issue item display |
| 43 | + |
| 44 | + The number is really a central information and not an internal one. |
| 45 | + |
| 46 | + In file INSTANCE/html/issue.item displays the creator, so one could add |
| 47 | + the number to it.:: |
11 | 48 |
|
| 49 | + <td class="form-text"><display call="reldate('creation', pretty=1)"> |
| 50 | + (<display call="plain('creator')">)</td> |
12 | 51 |
|
13 | | -Q: Displaying messages not only the summary |
| 52 | + to see:: |
14 | 53 |
|
15 | | -A: in instance/html/msg.index |
| 54 | + <td class="form-text"><display call="reldate('creation', pretty=1)"> |
| 55 | + (issue<display call="plain('id')"> by <display call="plain('creator')">)</td> |
16 | 56 |
|
17 | | - change |
18 | | - <td><display call="plain('summary')"></td> |
19 | | - to |
20 | | - <td><pre><display call="plain('content')"></pre></td> |
| 57 | +Installation |
21 | 58 |
|
22 | | - displays the whole message not only the first line and <pre> |
23 | | - prevents the browser from reformatting. |
| 59 | + Living without a mailserver. |
24 | 60 |
|
| 61 | + Remove the nosy reactor, means delete the file 'INSTANCE/detectors/nosyreactor.py'. |
25 | 62 |
|
| 63 | + Rights issues (MISSING) |
26 | 64 |
|
27 | | -Q: Getting the nosy list picker instead of textfield. |
| 65 | + Different jobs run under different users. |
28 | 66 |
|
29 | | - In classic template there is plenty of space below the text field. |
| 67 | + * Standalone roundup-server is started by whome ? |
30 | 68 |
|
31 | | -A: in instance/html/issue.item |
| 69 | + * Running cgi under apache. |
32 | 70 |
|
33 | | - At the file top set border=1 to see cell boundaries. |
| 71 | + * roundup-mailgw called via .forward from MTA, or running a cron job |
| 72 | + fetching via pop. |
34 | 73 |
|
35 | | - replace |
36 | | - <td class="form-text"><display call="field('nosy',size=20)"></td> |
37 | | - by |
38 | | - <td rowspan=5 class="form-text"><display call="menu('nosy',height=10)"></td> |
39 | 74 |
|
40 | | - remove the last cell in the next four rows, either by deleting a cell |
41 | | - or by reducing colspan. |
| 75 | +Troubleshooting |
42 | 76 |
|
| 77 | + mailgw bouncing |
43 | 78 |
|
| 79 | + messages are bouncing with the following error message.:: |
44 | 80 |
|
45 | | -Q: I wanted to see the issue id (the number) on the issue item display: |
| 81 | + Command died with status 1: |
| 82 | + "/usr/local/bin/python /usr/local/bin/roundup-mailgw /home/roundup". |
| 83 | + Command output: Traceback (most recent call last): |
| 84 | + File "/usr/local/bin/roundup-mailgw", line 178, in ? sys.exit(main(sys.argv)) |
| 85 | + File "/usr/local/bin/roundup-mailgw", line 153, in main db = |
| 86 | + instance.open('admin') AttributeError: '_roundup_instance_1' module |
| 87 | + has no attribute 'open' |
46 | 88 |
|
47 | | -A: |
48 | | - In file INSTANCE/html/issue.item change, showed e.g. "(anonymous)" |
49 | | - <td class="form-text"><display call="reldate('creation', pretty=1)"> |
50 | | - (<display call="plain('creator')">)</td> |
| 89 | + |
| 90 | + Happens when roundup-mailgw is called by a user that doesn't have |
| 91 | + read/execute permissions to the instance_home directory and sub |
| 92 | + directories. |
51 | 93 |
|
52 | | - to to see "( |
53 | | - <td class="form-text"><display call="reldate('creation', pretty=1)"> |
54 | | - (issue<display call="plain('id')"> by <display call="plain('creator')">)</td> |
| 94 | + An easy way to test whether it's a permissions problem, or some other mail |
| 95 | + server configuration problem is to cat an email-formatted text file |
| 96 | + directly to the roundup-mailgw script as the roundup user.:: |
55 | 97 |
|
56 | | -Q: Living without a mailserver. |
| 98 | + cat issue.txt | /usr/local/bin/roundup-mailgw /home/roundup |
57 | 99 |
|
58 | | -A: Remove the nosy reactor - delete the file |
59 | | - <instance home>/detectors/nosyreactor.py |
| 100 | + If that doesn't raise any errors, the problem is the permissions of the |
| 101 | + MTA. |
60 | 102 |
|
0 commit comments