Guess this is a "release process" issue :-)

Perhaps a "continuous build" and unit testing framework could be implemented to test all release candidates for regression on previously reported bugs and compatibility issues?

There is always this one issue that pops right after a release ;)

I use continuous integration, unit testing, and other agile development aspects in my "day" life (in .NET domain) and I totally believe in it.

I am trying to refactor the Mantis APIs to be more unit testable and researching available PHP unit testing frameworks (any suggestions welcome!).

However, this task was in config_defaults_inc.php, which I am not planning to unit test (same for all script pages). I am only planning to move as much logic out of them as possible (this was the original target, but in some cases we can still do a better job). The reason I am not unit testing scripts is that they require an Http unit testing engine, which in this case won't be really unit testing.

That said, the code that had the issue, can probably move to an API, and hence, it can be unit tested.

Short answer, we will get there (in N years), would you like to help? ;)

Yes I could help, at least testing or correction of mistakes

I just committed the change

Just my $.02 worth:

I know the efficiency difference is very small, but the PHP5 function is faster than the suggested fix. I would suggest the following to allow for both versions.

$t_soap_api_path_pos = (function_exists('stripos')) ? (stripos( $t_path, $t_soap_api_path )) : (strpos( strtolower( $t_path ), $t_soap_api_path ));