Any dev, do you know if the database schema is stable enough for me to try a git bisect between the 1.1.2 ( known good ) and 1.2.0a2 ( known bad) ?

There are database schema changes between 1.1.2 and 1.2.0a2.

Can I somehow apply the schema changes step-by-step? I see no instructions at http://www.mantisforge.org/dev/manual/en/developers/dev.database.install.html

I've narrowed it down to the fact that the soap api expects the filter_string to contain a '#' if the filter is valid, when in fact a filter with no filter criteria has a filter_string of '0', as seen in

mysql> select * from mantis_filters_table where id = 1;

+----+---------+------------+-----------+------------+---------------+

| id | user_id | project_id | is_public | name       | filter_string |

+----+---------+------------+-----------+------------+---------------+

|  1 |       1 |          0 |         1 | All issues | 0             |

+----+---------+------------+-----------+------------+---------------+

1 row in set (0.00 sec)

Then in mc_filter_api, line 152 we have

        $t_filter_detail = explode( '#', $t_filter, 2 );

    if( !isset( $t_filter_detail[1] ) ) {
            return new soap_fault( 'Server', '', 'Invalid Filter ( id = '.$p_filter_id.')' );
    }</pre>
So I think that the issue title should be changed to 'Unable to retrieve issue headers for filter without criteria'.
I'm not sure about the fix though. Perhaps the serialization code simply needs to write a proper filter_string entry for such a filter. Let me know if you agree and I'll start digging.
	

No idea how I ended up creating this bug, but:

1. I can't create that filter using the web interface anymore
2. Manually adding such a filter result in a web interface error: 'The filter you are trying to use is too old to be upgraded, please re-create it'