I think this is fixed in CVS, so as soon as we release 0.18.0a3...

No, I don't think it is. My hunch is that the problem occurs only until you have ever selected a project. There are still some functions in the print API at least that use $g_project_cookie_val or whatever. Until you've set a project, this will not be set. If you use helper_get_current_project() however, it will return a default project of 0 if no project is set.

Oh, actually, that doesn't quite make sense because you shouldn't be able to report a bug without selecting a project. Anyway, I'm still a little suspicious and I'm going to assign this to myself and look at it again.

If you know of a specific commit that actually consciously fixed this then please close it again. But if you're just not seeing it anymore, I suspect it may still be there for new users.

hi jfitzell,
maybe I can help:
a) yes, I selected a "default" project for me in the old mantis and the movement to the new database did contain this selection.

But, what do you mean with "new users" - I think, I'm an old user :-)

For whatever combination of reasons, this seems to be fixed. And I fixed what I thought might have been the cause for new users.