Relationship Graph
View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0012431 | mantisbt | db mysql | public | 2010-10-06 23:52 | 2012-02-06 11:42 |
Reporter | fonnnnnn | Assigned To | atrol | ||
Priority | high | Severity | major | Reproducibility | always |
Status | closed | Resolution | no change required | ||
Platform | linux | OS | CentOS | OS Version | 5.4 |
Product Version | 1.2.3 | ||||
Summary | 0012431: APPLICATION ERROR 0001502 Category not found. | ||||
Description | i have a problem with role of administrator it displays "APPLICATION ERROR 0001502 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." i cannot visit "view_all_bug_page.php and my_view_page.php" but other pages it works. i found that the database has a problem (i remove folder mantis to test other server and it not occur again.) but i don't know which tables that has a problem and what should i do to solve this? any idea? thanks | ||||
Tags | No tags attached. | ||||
i found the solution. Because of some project error so i cannot view bug reports. i cannot view all project, but some project works. Delete project that cause error can solve this. i will share this for someone who has same problem with me. thanks all, |
|
Does your note mean that the issue can be closed? |
|
i don't know the cause of an error project , i think it may be result of my error config or installation of some plugin. You can close this issue. |
|
I also find this issue, I try to move a issue from one projcet to anther, this happened. Two projects have diffent category. One project's category comes from global setting, Another's is defined for it's own. |
|
How do you do to move your issue? |
|
Do you have any backup of your database? |
|
I have the same issue. It happend after I moved an issue to another project. It was a Normal operation every user can do. Since I hardly use Move before I never noticed before. The issue happned if the target project possibly did not contain the category in the original bug. It is quite some serious bug IMHO. I could solve it by directly manipulating the Database values and delete some. But I do not expect others to be able to do that. Th issue was Category 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. |
|
I had this same issue, when trying to copy several issues from various projects to a new project that didn't have the same categories. I made the categories in the new project and tried to resubmit, but it seemed to still have problems, and got the same APPLICATION ERROR # 1502 I went in and saw one of the bugs had a category ID of 1 in the mantis_bug_table so manually changed that to be the same as the others in that project and everything sprang to life |
|
This issue is NOT resolved but I receive Access Denied message when attempting to re-open. MantisBT Version 1.2.5 I'm using a new install of this version that had been working fine. I was playing with categories and projects as I try and understand the best architecture. At one point I moved an issue from a project into a sub-project. I believe it asked for a category and I selected and then the Issue essentially became corrupt. I am unable to access it or any page that tries to display it, giving the aforementioned issue application error. I'm going to try and manually edit the database because actually accessing the ticket to correct the problem seems impossible. -- Okay, confirmed, manually editing the MySQL mantis_bug_table, choosing the offending issue ID, and then setting it's category id value to a known good value fixed the issue. I'm not sure how it was corrupted in the first place, apparently MantisBT allows invalid Category IDs to be set on Move action. |
|
I did the exact same thing as LeonardChallis, it showed the exact same error. I also encountered an entry in the mantis_bug_table with category_id set to 1, as soon as I updated it manually, everything started working again. I moved 2 bugs between categories, but only 1 of the bugs got the category_id set to 1. Our mantis version number is 1.2.5. |
|
Please check if the attached patch at 0013007 fixes the problem |
|