View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0022370 | mantisbt | upgrade | public | 2017-02-14 08:34 | 2017-02-25 15:22 |
Reporter | matroos | Assigned To | atrol | ||
Priority | normal | Severity | minor | Reproducibility | random |
Status | closed | Resolution | no change required | ||
Platform | Windows | OS | Windows Server | OS Version | 2008 R2 |
Product Version | 2.1.0 | ||||
Summary | 0022370: Application error 0000026 after upgrade from 1.2.19 to 2.1.0 | ||||
Description | On my test environment, I have upgraded to 2.1.0 three times now (every time from my original working 1.2.19), and in quite an arbitrary way, upon clicking an issue to navigate to its details page, I get this "application error 0000026". I have been searching around on the internet and on the forum, but could not find anything that can solve my case. Did something go wrong during database conversion? I have upgraded from 1.2.19. | ||||
Steps To Reproduce | Happens when trying to navigate to the details page of some of the issues. Does not happen on all of them. | ||||
Additional Information | APPLICATION ERROR 0000026 Variable Value Type Filename Line Function Args D:\MantisBT - Copy\core\helper_api.php 189 - - trigger_error ( <string>'26', <integer>256 ) | ||||
Tags | No tags attached. | ||||
Would it make a difference if I would first upgrade to 1.3.6 and then to 2.1.0 from there on? |
|
No. There is no difference in database schema between 1.3.6 and 2.1.0. |
|
OK. So tried to migrate from 1.2.19 to 1.3.6 anyway. And I have the same arbitrary "application error 26". This time experienced it when I tried to assign an issue to someone else with "feedback". |
|
Found the solution. Also had an issue with disappearing due dates and errors when trying to alter due dates (or manually entering them). That got solved by entering a missing trailing double quote in the bug_change_status_page.php (line 245). Seems I'm now ready to put 2.1.0 into production. This issue can be closed. |
|
Thanks for the feedback!
Will be fixed in 2.2.0, see 0022288 |
|