With Roundup-0.7.8, if you enter an URL manually into a
web browser to access an issue, like "/issue8",
everything is right.
But if you enter an URL like "/issue08", Roundup
display a form with issue8 values, but with missing
informations which seems to correspond with MultiLink
values, like "superceder", "nosy list" or "messages" ;
history seems to be displayed normally, except for some
"link/unlink" events.
The same kind of problem seems to appear with every
class having multilink properties.

With this kind of URL, Roundup should :
 - display an error message, or
 - get access to the correct instance, without any
missing value.


  Thierry

Logged In: YES 
user_id=8719

checked in the HEAD branch: leading zeroes in the ID part of
the node designator are ignored.

note that inconsistent were only RDBMS backends; anydbm was
saying "nothing found" for node designators like 'issue08'.

Logged In: YES 
user_id=32092

Following the last comment, I should add that I'm using the
PostgreSQL backend...

  Thierry

Logged In: YES 
user_id=6405

I'm not convinced this should be "fixed". I think the 
determine_context method should raise "not found" on invalid 
designators like this... just so people don't get used to using 
them and then finding it breaks in other places that expect no 
padding. 

Logged In: YES 
user_id=8719

inconsistence should be fixed without any doubt.

if you don't like ignoring the leading zeroes, then URL
regexp should be modified to disallow leading zero in the id
part of the designator.

Logged In: YES 
user_id=6405

Fixed in 0.8