Avoid errors from selecting "no selection" on multilink (issue2550722). As discussed in issue 2550722 there are various cases where selecting "no selection" on a multilink can result in inappropriate errors from Roundup: * If selecting "no selection" produces a null edit (a value was set in the multilink in an edit with an error, then removed again, along with all other changes, in the next form submission), so the page is rendered from the form contents including the "-<id>" value for "no selection" for the multilink. * If creating an item with a nonempty value for a multilink has an error, and the resubmission changes that multilink to "no selection" (and this in turn has subcases, according to whether the creation then succeeds or fails on the resubmission, which need fixes in different places in the Roundup code). All of these cases have in common that it is expected and OK to have a "-<id>" value for a submission for a multilink when <id> is not set in that multilink in the database (because the original attempt to set <id> in that multilink had an error), so the hyperdb.py logic to give an error in that case is thus removed. In the subcase of the second case where the resubmission with "no selection" has an error, the templating code tries to produce a menu entry for the "-<id>" multilink value, which also results in an error, hence the templating.py change to ignore such values in the list for a multilink.

.TH ROUNDUP-SERVER 1 "27 July 2004"
.SH NAME
roundup-demo \- create a roundup "demo" tracker and launch its web interface
.SH SYNOPSIS
\fBroundup-demo\fP [\fIbackend\fP [\fBnuke\fP]]
.SH OPTIONS
.TP
\fBnuke\fP
Create a fresh demo tracker (deleting the existing one if any). If the
additional \fIbackend\fP argument is specified, the new demo tracker will
use the backend named (one of "anydbm", "sqlite", "metakit", "mysql" or
"postgresql"; subject to availability on your system).
.SH DESCRIPTION
This command creates a fresh demo tracker for you to experiment with. The
email features of Roundup will be turned off (so the nosy feature won't
send email). It does this by removing the \fInosyreaction.py\fP module
from the demo tracker's \fIdetectors\fP directory.

If you wish, you may modify the demo tracker by editing its configuration
files and HTML templates. See the \fIcustomisation\fP manual for
information about how to do that.

Once you've fiddled with the demo tracker, you may use it as a template for
creating your real, live tracker. Simply run the \fIroundup-admin\fP
command to install the tracker from inside the demo tracker home directory,
and it will be listed as an available template for installation. No data
will be copied over.
.SH AUTHOR
This manpage was written by Richard Jones
<richard@users.sourceforge.net>.