Skip to content

Commit 07ff02d

Browse files
author
Richard Jones
committed
instance -> tracker, node -> item
1 parent 2e7032b commit 07ff02d

File tree

12 files changed

+395
-465
lines changed

12 files changed

+395
-465
lines changed

doc/FAQ.txt

Lines changed: 3 additions & 90 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
Roundup FAQ
33
===========
44

5-
:Version: $Revision: 1.9 $
5+
:Version: $Revision: 1.10 $
66

77
NOTE: This is just a grabbag, most of this should go into documentation.
88

@@ -12,65 +12,14 @@ NOTE: This is just a grabbag, most of this should go into documentation.
1212
Changing HTML layout
1313
--------------------
1414

15-
Note changes to the files in html take place immediatly without
16-
restart, even when running roundup-server.
17-
18-
Displaying whole messages not only the summary
19-
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
20-
21-
Modify instance/html/msg.index change::
22-
23-
<td><display call="plain('summary')"></td>
24-
25-
to::
26-
27-
<td><pre><display call="plain('content')"></pre></td>
28-
29-
displays the whole message not only the first line and 'pre'
30-
prevents the browser from reformatting.
31-
32-
Getting the nosy list picker instead of textfield
33-
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
34-
35-
In classic template there is plenty of space below the text field.
36-
So one could modify instance/html/issue.item to use it.
37-
38-
At the file top set 'border=1' to see cell boundaries, then
39-
replace::
40-
41-
<td class="form-text"><display call="field('nosy',size=20)"></td>
42-
43-
by::
44-
45-
<td rowspan=5 class="form-text"><display call="menu('nosy',height=10)"></td>
46-
47-
and remove the last cell in the next four rows, either by deleting a cell
48-
or by reducing colspan.
49-
50-
Want to see the issue id (the number) on the issue item display
51-
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
52-
53-
The number is really a central information and not an internal one.
54-
55-
In file INSTANCE/html/issue.item displays the creator, so one could add
56-
the number to it.::
57-
58-
<td class="form-text"><display call="reldate('creation', pretty=1)">
59-
(<display call="plain('creator')">)</td>
60-
61-
to see::
62-
63-
<td class="form-text"><display call="reldate('creation', pretty=1)">
64-
(issue<display call="plain('id')"> by <display call="plain('creator')">)</td>
65-
6615
Installation
6716
------------
6817

6918
Living without a mailserver.
7019
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
7120

72-
Remove the nosy reactor, means delete the file
73-
'INSTANCE/detectors/nosyreactor.py'.
21+
Remove the nosy reactor, means delete the tracker file
22+
'detectors/nosyreactor.py'.
7423

7524

7625
Rights issues (MISSING)
@@ -91,42 +40,6 @@ see Troubleshooting_.
9140
Troubleshooting
9241
---------------
9342

94-
AttributeError: '_roundup_instance_1' module has no attribute 'open'
95-
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
96-
97-
For example submitting issues via roundup-mailgw breaks similar to this::
98-
99-
Command died with status 1:
100-
"/usr/local/bin/python /usr/local/bin/roundup-mailgw /home/roundup".
101-
Command output: Traceback (most recent call last):
102-
File "/usr/local/bin/roundup-mailgw", line 178, in ?
103-
sys.exit(main(sys.argv))
104-
File "/usr/local/bin/roundup-mailgw", line 153, in main
105-
db = instance.open('admin')
106-
AttributeError: '_roundup_instance_1' module has no attribute 'open'
107-
108-
Happens if the user which accesses the instance has no read right
109-
on 'INSTANCE/dbinit.py' or 'pyc'.
110-
111-
If the user has no rights on the 'INSTANCE/db' the mailgw finishes,
112-
but is, of course, unable to add the message. A notification to
113-
the roundup-admin is sent, with a longer trace ending in::
114-
115-
File "/opt/python/lib/python2.2/dbhash.py", line 16, in open
116-
return bsddb.hashopen(file, flag, mode)
117-
error: (13, 'Keine Berechtigung')
118-
119-
Replace 'Keine Berechtigung' by 'Not permitted' or ...
120-
121-
An easy way to test whether it's a permissions problem, or some other mail
122-
server configuration problem is to cat an email-formatted text file
123-
directly to the roundup-mailgw script as the roundup user.::
124-
125-
cat issue.txt | /usr/local/bin/roundup-mailgw /home/roundup
126-
127-
If that doesn't raise any errors, the problem is the permissions of the
128-
MTA.
129-
13043
-----------------
13144

13245
Back to `Table of Contents`_

0 commit comments

Comments
 (0)