View Issue Details

IDProjectCategoryView StatusLast Update
0019550mantisbtbugtrackerpublic2015-04-19 06:37
Reporterrkorebrits Assigned Todregad  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionno change required 
Product Version1.3.0-beta.2 
Summary0019550: After updating an status, APPLICATION ERROR #1100 appears
Description

We just upgraded to version 1.3.0-b2 and now when we update the status of an issue, we receive the following error:

APPLICATION ERROR #1100
Issue 1 not found.
Please use the "Back" button in your web browser to return to the previous page. There you can correct whatever problems were identified in this error or select another action. You can also click an option from the menu bar to go directly to a new section.

One other thing that I notices (not sure if this is new), is that when updating an issue, the button to "save" reads: [New Issue]. Even though I'm on bug_change_status_page.php

Steps To Reproduce
  • Go to an existing ticket.
  • Change the status (e.g. to "acknowledged")
  • Save
  • Error page shows
TagsNo tags attached.
Attached Files
Capture.JPG (72,966 bytes)   
Capture.JPG (72,966 bytes)   

Activities

rkorebrits

rkorebrits

2015-03-25 05:14

reporter   ~0049293

This also happens when I click the [Assign to] button

dregad

dregad

2015-03-25 06:20

developer   ~0049294

I was not able to reproduce your problem with a fresh install of MantisBT 1.3.0b2, and it is also not reproducible on this tracker (running the same).

Additional information listed below may be useful:

  • Exact version of MantisBT, PHP, Database, Web server, Browser and Operating System
  • Relevant customizations (e.g. changes in config_inc.php, etc)
  • Installed plugins or custom functions ?
  • Was the MantisBT source code modified in any way ?

You may also want to enable detailed errors to get a better understanding of the problem. Temporarily set

$g_show_detailed_errors = ON;

WARNING - SECURITY RISK: the 'show_detailed_errors' config can cause MantisBT to display sensitive information about your system. We recommend to restrict its activation to a Test environment, only for as long as necessary. If possible, do not turn it ON globally, instead limit it for specific user(s) using the Manage Configuration page.

atrol

atrol

2015-04-08 18:07

developer   ~0049352

rkorebrits,

You did not provide any feedback; I am therefore resolving this issue as "no change required".

Feel free to reopen the issue at a later time and provide the requested information.