View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0010472 | mantisbt | custom fields | public | 2009-05-08 10:10 | 2019-12-13 18:06 |
Reporter | KarolinaR | Assigned To | dregad | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | unable to reproduce | ||
Product Version | 1.1.7 | ||||
Summary | 0010472: Custom fields are missing separators | ||||
Description | I guess it's a side effect of 0009606 due to the fact that the line in custom_field_api.php: $c_value=db_prepare_string( custom_field_value_to_database( $p_value, $t_type ) ); has been changed to: Missing function "custom_field_value_to_database" causes that custom fields are inserted to database in the form: This causes problems with the filtering of the custom fields. | ||||
Steps To Reproduce |
Is it a bug or is it a feature? ;-) | ||||
Tags | No tags attached. | ||||
The feature is really confused. The database has a mix of entries with and without leading and trailing brackets depending on when the feature was created. The best solution is probably to remove the bars, on the assumption that entries wouldn't have the same subset of strings. |
|
So you mean that instead of changing you want to get rid of the bars like this: How do you want to solve the issue of the same subset of strings here? BR, |
|
We are resolving this issue, because it was reported against an old version of MantisBT which is no longer supported, and the problem can't be reproduced in the latest version. If the problem still exists, do not hesitate to reopen the issue. |
|