View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0025002||mantisbt||custom fields||public||2018-11-22 05:59||2019-01-02 17:25|
|Target Version||2.19.0||Fixed in Version||2.19.0|
|Summary||0025002: Error when updating content in a custom field of type "Text Area" ("Textbereich"): History cannot be stored|
While updating the text within a custom field of type "Text Area", we get the error Message:
Column 'old_value' in table mantis_bug_history_table is 'varchar 255', but should be 'longtext'? Same for column 'new_value'?
|Steps To Reproduce|
Write a long text (more then 255 characters) into a custom field of type Text Area. Store the entry. Then edit that entry, do some change to the text. Store that entry.
The error does not occure when using only short text.
|Tags||No tags attached.|
This should be fixed since version 2.13.0 see 0024056.
Forget my previous note, I think I understand now what happened.
I was not able to reproduce because MySQL on my test system was running in some kind of auto truncate mode.
MantisBT: master 4609e811
2018-11-22 16:16:56Details Diff
|Truncate values before writing to database history table
TEXTAREA custom fields can contain more than 255 characters.
Changing such fields fails, as the old value can't be stored
in history table.
This change fixes the issue by truncating the string.
|mod - core/history_api.php||Diff File|