Unable to delete enlistment

Avatar

Steffen Mueller

about 1 year ago

As a template for the enlistment of a new project, I copied the repository URL of another project in the same repository. Unfortunately, I was too quick in finalizing the enlistment and forgot to change the last part of the URL.

Afterwards, I tried to delete the wrong enlistment, but it didn't work. I get the JavaScript popup asking for confirmation and then, I get served an XML document (see below) claiming success. But the enlistment won't go away. You can find the problematic page at http://www.ohloh.net/projects/autoxs/enlistments

The XML I get served is attached below (slightly mangled, sorry.)

Anyone?

Cheers, Steffen

{response} {status} success{/status} {result} {enlistment} {id}24001{/id} {projectid}13139{/projectid} {repositoryid}19781{/repositoryid} {repository} {id}19781{/id} {type}SvnRepository{/type} {url}http://svn.ali.as/cpan/trunk/Algorithm-CurveFit{/url} {username/} {password/} {loggedat}2008-04-01T21:26:46Z{/loggedat} {commits}1{/commits} {ohlohjobstatus}success{/ohlohjobstatus} {/repository} {/enlistment} {/result} {/response}


Avatar

Robin Luckey

about 1 year ago

Hi Steffen,

There are a lot of little puzzles here.

When you say you "tried to delete the wrong enlistment", does that mean you simply clicked the "Delete" link next to the enlistment? And in response to this you received XML?!? If the answer is yes, I'd be curious what browser/OS you are using. This sounds like a very odd bug in our site.

As far as I can tell, 'delete' is working for me, so if you just let me know which enlistments you want deleted, I can take care of that.

Thanks, Robin


Avatar

Christopher Lenz

about 1 year ago

I'm seeing the same issue (with the CouchDB project which has some obsolete/incorrect enlistments). Tried with Safari 3.1 and Firefox 3.0b4, both on Leopard.

Clicked "Delete", get Javascript confirmation dialog, clicked "Okay", get XML response with okay.

The enlistments don't actually seem to get deleted, though.


Avatar

Robin Luckey

about 1 year ago

This is now fixed.

It was a bizarre consequence of changing from project ID numbers to project names in the URL.

Thanks for reporting it. Let me know if you find any more trouble,

Robin