Category has been disabled

[amphetamine]

after upgrading the system to 27.1
in view issue detail page, category field has red triangle exclamation mark (Category has been disabled, please select another one)

Go to manage>projects, check Global Categories, all the categories are empty. Then try to edit each of the category, tick the enabled checkbox and updated the category. only the default category "general" cannot be updated and shown

Code: Select all

APPLICATION ERROR #1504

Operation cannot be completed, because Category "General" is defined as Default For Moves in at least one project or globally.

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.

[atrol]

Did you run a database upgrade?

[amphetamine]

Did you run a database upgrade?

Thank you!
Issue fixes

[Skye]

Same problem here, database upgrade went poorly.

My mantis user has full permission to (that particular) database, it should have been able to run the 'alter' command. But instead it displayed some message about not being able to do it, and gave me the SQL. Weird, but no big deal, I just manually ran the commands it gave me:

Code: Select all

-- MantisBT 2.27.1 Database creation script
-- 2025-04-05T02:44:13+00:00

SET NAMES UTF8;

-- Schema step 212
ALTER TABLE category MODIFY COLUMN status INTEGER UNSIGNED NOT NULL DEFAULT 1;

-- Schema step 213
-- Execute PHP Update Function: install_category_status_default()

-- Set database version
UPDATE config SET value = 213 WHERE config_id = 'database_version' AND project_id = 0 AND user_id = 0;

No errors on the commands.

I then reloaded the install page and continued the install, all green.

However, now when I go to enter bugs, no categories can be selected. So something definitely did not go to plan. What is correct way to migrate?

Update: I set the status field to 1 for each of the categories and now they seem to work again. If there was any other SQL it should have given me but didn't, please let me know.