View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0010923 | mantisbt | bugtracker | public | 2009-09-10 05:44 | 2018-03-01 03:04 |
Reporter | wschneider | Assigned To | vboctor | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | no change required | ||
Product Version | 1.2.0rc1 | ||||
Summary | 0010923: function history_log_event_direct should check (and eventually truncate) the length of the new and the old value | ||||
Description | We get an error if we submit tickets with custom fields (textfields) where the length of the text exceeds the length of 255 characters. | ||||
Additional Information | I patched the problem this was: function history_log_event_direct( $p_bug_id, $p_field_name, $p_old_value, $p_new_value, $p_user_id = null, $p_type = 0 ) { Only log events that change the valueif( $p_new_value != $p_old_value ) { $c_field_name = $p_field_name; #patch: $t_mantis_bug_history_table = db_get_table( 'mantis_bug_history_table' ); $query = "INSERT INTO $t_mantis_bug_history_table $result = db_query_bound( $query, Array( $c_user_id, $c_bug_id, db_now(), $c_field_name, $c_old_value, $c_new_value, $c_type ) ); | ||||
Tags | patch | ||||
My assumption is that this is not a bug in the out of the box MantisBT. You will only hit the problem if the custom field allows more than 255 which means that you have another patch installed. Is that correct? |
|
You're right. It is the patch given in 0006626, which causes the described problem. |
|