BugNET

You can clear your cookies/session and you'll be able to access the issues list again.

Also, if you are able to work within the source, I've posted a fix here: http://bugnetproject.com/Forums/tabid/54/forumid/6/threadid/5381/scope/posts/Default.aspx

Unfortunately getting a similar issue in version 0.9.152. If I change the issues per page to say 15, it redisplays the page correctly with 15 issues. If I click on Home, and then go back into the project, it gives this error :

2012-02-08 06:46:26,985 [8] ERROR BugNET.Global [(null)] - Application Error


System.Web.HttpUnhandledException (0x80004005): Exception of type 'System.Web.HttpUnhandledException' was thrown. ---> System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
at System.ThrowHelper.ThrowArgumentOutOfRangeException()
at BugNET.UserControls.DisplayIssues.InsertCustomFieldData()
at BugNET.UserControls.DisplayIssues.DataBind()
at BugNET.Issues.IssueList.BindIssues()
at BugNET.Issues.IssueList.Page_Load(Object sender, EventArgs e)
at System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e)
at System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e)
at System.Web.UI.Control.OnLoad(EventArgs e)
at BugNET.UserInterfaceLayer.BasePage.OnLoad(EventArgs e)
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.HandleError(Exception e)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest()
at System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context)
at System.Web.UI.Page.ProcessRequest(HttpContext context)
at ASP.issues_issuelist_aspx.ProcessRequest(HttpContext context)
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)


To resolve the issue, I appear to have to go into a different project and display its issues first, then go back to the project I changed the issues per page on.