I was able to reproduce this as well. It may be related to installer failing due to 0034783 and hence not running the appropriate steps. Updating the category logic seems to fail without checking the change being applied to the category. For example, enabling a category shouldn't conflict with it being the default, yet disabling it does conflict.

@webaware

All categories were suddenly unavailable, so I had to enable each category at the All Projects level

This is not a normal situation, the installer includes an update step (213) that should have set the status of all categories to 1 (Enabled).

For some reason this failed for you, we need to figure out why. Did you notice any errors during the upgrade ? What is your current Database Schema Version ?

As for fixing error 1504, you have 2 options:

• temporarily change the default category to something else, enable General category and restore it as default
• SQL UPDATE mantis_category_table SET status = 1 WHERE id = ...

I would also recommend to check the default value for mantis_category_table.status column, it should be 1.

@vboctor

installer failing due to 0034783 and hence not running the appropriate steps

But in that case you should get an error / notification that your schema is out of date...

Updating the category logic seems to fail without checking the change being applied to the category

You mean in install_category_status_default() function ? Or when updating a category from Manage / Edit Project pages ?

My apologies, DB schema was still at 211. I have run the update procedure and it's now 213, and all categories are enabled including General. I thought I'd done it, but it would seem I did not!

Also, default for mantis_category_table.status is 1.

Thanks for your attention, and again, my apologies.

Thanks for the feedback.