Mantis Bug Tracker - Forums

I've figured out a workaround for my specific issue. I edited two core files so that the filter will work with the old entries (the ones with "|" around it) and new entries.

around line 1210 of core/filter_api.php, modify the line:

array_push( $t_filter_array , db_helper_like( "$t_table_name.value ...

I've looked into this further....I am using a "Multiselection list" custom field. Each selection is delimited by a '|' and apparently the older version of Mantis (1.0.6) stores the string in the mantis_custom_field_string_table with the "|" on each end of the string. For example if you have an entry ...

I recently upgraded from 1.0 to 1.1.7. I've worked out some upgrade issues on my own except for one that is baffling me. I am using custom fields. Before the upgrade I was able to filter searches (View Issues) using these fields. After upgrading to 1.1.7, the filter still works for records that have ...

Here's a snippet of code that I am using to redirect http request to the https version of the site. I had to use this to avoid using .htaccess method of redirection. Add this code to core.php right after the ob_start ('compress_handler' ) call:


if ( isset ( $_SERVER['HTTPS'] ) != 'on' ) {
$g ...