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