Same problem here after upgrading from 1.1.8 to 1.2.1

Quick'n'dirty fix:

function bug_revision_exists( $p_revision_id ) {
if (empty($p_revision_id)) { return false; } // <-- add this line
$t_bug_rev_table = db_get_table( 'mantis_bug_revision_table' );

in core/bug_revision_api.php

Seems to do the trick for us. Thanks, smig1o, for tracking the problem down.

[edit: fixed stupid copy&paste error]

I did same 'quickfix'. But I am waiting for official patch.

I had the same problem, upgrading from 1.1.6 to 1.2.1
+1 for this quickfix
Thank you

We have the same problem, after migration from 1.2.0a3 to 1.2.1:

APPLICATION ERROR 0000401
Database query failed. Error received from database was 0001146: Table 'bugtracker.mantis_bug_revision_table' doesn't exist for the query: SELECT * FROM mantis_bug_revision_table WHERE id=''.

I reinsert the error message with a space after the # so error codes are not escaped like bug ids:

APPLICATION ERROR # 401
Database query failed. Error received from database was # 1146: [...]

In my case, for some reason during the installation the database was not upgraded, so the mantis_bug_revision_table was not created and the dates were not migrated (i always saw the default date 1970-1-1)
I realaunched the installation from a different docroot then the batabase has benn correctly update and now it works.

dhaun,

i got same problem, you path works fine. Thank you

This problem still exists in Mantis 1.2.4. My above workaround "fixes" the problem for now, but could someone from the Mantis team please comment on this issue?

I filed a bug @ 0012513 which contains a more technical reason to why this issue is a problem. The comment from this bug (which I have now resolved as a duplicate of this one) is:

Within history_api, the history_localize_item function is calling the bug_revision_exists function of bug_revision_api with the wrong argument type. It should be sending an integer, not a string.

As bug_revision_api doesn't use db_prepare_int when building queries this error will result in SQL query execution errors when an integer field in the database is compared to the supplied string (type mismatch).

This is in the patch queue now :)

Committed.