Which version of Mantis are you using? What were you trying to do when you got such error?

V 0.18.2
I just wanted to clean up the system before I launch it.
You might want to look at the erroneous bug at
<URL removed after bug has been resolved>

Btw: Any way to set up the system to get email-notifications when new users sign in?

edited on: 03-21-04 10:53

vboctor:
u c,y would u ask which version? mantis,a bug tracking tool, when report a bug, still need to ask the reporter "which version"?!!

y didn't u add the version field in the database?? i think there r 2 version fields needed: the version the bug rise, and the version the bug resolved when change the status to Resolved.

we r using matis for our bug-tracking,it's a wonerfull tool~! but the important featcher we need, to track bug by version, it has not. we try to add by ourselves, but there r some problems: if we modify the database schema, we will meet the update problem when new version of mantis released;if we use the custom field, maybe we can not get the quick search advantage, and still, the update problem when mantis add this featcher.

There is a version field for the report but only in the advanced report.
However, including a field "fixed in release" could have the advantage, that it would add the possility to generate a change-history out of Mantis.

This worked for me. Change the line in user_api.php, function user_get_field() from:
$row = user_get_row( $p_user_id );

To:

To avoid "User not found" error

  # $row = user_get_row( $p_user_id );
  $row = user_cache_row( $p_user_id, false );
  if ( false === $row ) {
     return '';
  }

Thanks JimB, after this change I was able to delete this damaged db-entry.

It appears that this is fixed in the 0.19 alpha's already