View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0009698 | mantisbt | bugtracker | public | 2008-10-15 18:31 | 2009-06-26 11:59 |
| Reporter | cyrus13 | Assigned To | jreese | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | unable to reproduce | ||
| Platform | Firefox 3.0.3 | OS | Windows XP | ||
| Product Version | git trunk | ||||
| Summary | 0009698: APPLICATION ERROR #2800 when submitting two issues in a row. | ||||
| Description | I am getting an APPLICATION ERROR #2800 if I try to submit two issues in a row. The first issue I submit goes through, but the second issue I try to submit I get an APPLICATION ERROR #2800. I am using the code from r5673 of the trunk folder on svn. (I guess this is related to bug 0009691, which has been fixed) | ||||
| Steps To Reproduce |
| ||||
| Additional Information | A workaround is to logout and login after every single bug report. | ||||
| Tags | No tags attached. | ||||
|
After applying the fixes from SVN rev5668 only on a plain v1.1.3 installation this works fine here. |
|
|
I can't reproduce this issue in either 1.1.x or trunk; I think this may have been a side effect of issue 0009323 with regards to browser caching of form pages. |
|
|
Good morning, I have updated to issue 1.1.4 a few days ago and I am getting reports of this issue. The users are using IE6. It does not seam to occur on Firefox 3.0.3, and rebooting does not clear the problem. It appears after the users have submitted one issue. It can be solved by clearing the temporary working data. |
|
|
After updating to v1.1.5 I get this problem. Running Firefox 3.0.4 so it's not just on IE. It doesn't help to logout and then login again between the reports, but forcing a refresh (Ctrl+F5) works. Is rev5668 newer than 1.1.5? In that case I can check if that works for me. |
|
|
On 1.1.5 it only works when pressing Ctrl + F5. In any other ocasion, the APPLICATION ERROR #2800 pops up. |
|
|
Still getting the same error in 1.1.6 |
|