@@ -155,26 +155,16 @@ text/html. This is done with::
155155if you were returning a PNG image.
156156
157157
158- Added CSV export action
159- -----------------------
160-
161- A new action has been added which exports the current index page or search
162- result as a comma-separated-value (CSV) file.
163-
164- To use it, add this to your "index" templates::
165-
166- <a tal:attributes="href python:request.indexargs_url('issue',
167- {'@action':'export_csv'})">Download as CSV</a>
168-
169- Making sure that the ``'issue'`` part matches the class name of the page
170- you're editing.
171-
172158Roundup server
173159--------------
174160
175161The roundup-server web interface now supports setgid and running on port
176162< 1024.
177163
164+ It also forks to handle new connections, which means that trackers using
165+ the postgresql or mysql backends will be able to have multiple users
166+ accessing the tracker simultaneously.
167+
178168
179169HTML templating made easier
180170---------------------------
@@ -238,6 +228,33 @@ may use the new ``utils.url_quote(url)`` and ``utils.html_quote(html)``
238228methods.
239229
240230
231+ CSV download of search results
232+ ------------------------------
233+
234+ A new CGI action, ``export_csv`` has been added which exports a given
235+ index page query as a comma-separated-value file.
236+
237+ To use this new action, just add a link to your ``issue.index.html``
238+ page::
239+
240+ <a tal:attributes="href python:request.indexargs_url('issue',
241+ {'@action':'export_csv'})">Download as CSV</a>
242+
243+ You may use this for other classes by adding it to their index page and
244+ changing the ``'issue'`` part of the expression to the new class' name.
245+
246+
247+ Other changes
248+ -------------
249+
250+ - we serve up a favicon now
251+ - the page titles have the tracker name at the end of the text instead
252+ of the start
253+ - added url_quote and html_quote methods to the utils object
254+ - added isset method to HTMLProperty
255+ - added search_checkboxes as an option for the search form
256+
257+
241258Email Interface
242259===============
243260
@@ -285,6 +302,10 @@ In addition, the ``IssueClass`` methods ``nosymessage()`` and
285302message id parameter. This means that change notes with no associated
286303change message may now be generated much more easily.
287304
305+ The roundupdb nosymessage() method also accepts a ``bcc`` argument which
306+ specifies additional userids to send the message to that will not be
307+ included in the To: header of the message.
308+
288309
289310Registration confirmation by email
290311----------------------------------
@@ -293,6 +314,23 @@ Users may now reply to their registration confirmation email, and the
293314roundup mail gateway will complete their registration.
294315
295316
317+ ``roundup-mailgw`` now supports IMAP
318+ ------------------------------------
319+
320+ To retrieve from an IMAP mailbox, use a *cron* entry similar to the
321+ POP one::
322+
323+ 0,10,20,30,40,50 * * * * /usr/local/bin/roundup-mailgw /opt/roundup/trackers/support imap <imap_spec>
324+
325+ where imap_spec is "``username:password@server``" that specifies the roundup
326+ submission user's IMAP account name, password and server. You may
327+ optionally include a mailbox to use other than the default ``INBOX`` with
328+ "``imap username:password@server mailbox``".
329+
330+ If you have a secure (ie. HTTPS) IMAP server then you may use ``imaps``
331+ in place of ``imap`` in the command to use a secure connection.
332+
333+
296334Database configuration
297335======================
298336
0 commit comments