0014047: Moving issue between projects results in inoperable site if category doesn't exist in destination project

ID	Project	Category	View Status	Date Submitted	Last Update
0014047	mantisbt	administration	public	2012-03-14 19:17	2012-03-25 15:08

Reporter	mike_hcn	Assigned To	atrol
Priority	normal	Severity	crash	Reproducibility	have not tried
Status	closed	Resolution	duplicate
Product Version	1.2.8

Summary	0014047: Moving issue between projects results in inoperable site if category doesn't exist in destination project
Description	Please forgive me if this is a duplicate of something you've already seen. I did search, but didn't find this problem described anywhere. When I move an issue from Project A to Project B, but the issue's category does not exist in Project B, the site becomes inoperable with an error at the top: "Category not found." I've reproduced this myself a couple of times. The only fix I've found is to manually go into the MySQL table and change the category ID for that issue to a category id value that IS found in Project B.
Tags	No tags attached.

atrol 2012-03-14 19:25 developer ~0031469	Are you able to fix the issue by following the steps provided at 0013850 ?

mike_hcn 2012-03-15 10:52 reporter ~0031475	That was it - we had deleted that original "General" category when first setting up and configuring Mantis. We've since added it back and updated the g_default_category_for_moves variable in the config file to match. Many thanks! Sorry I missed that solution when searching.