It does not only "not store" the changes, but it deletes the content! If there is some text in the content database field, and then I store an update text, result is an empty content field. Thus it does write to the database. And why should it store the content in an other database filed than what it belongs to? If it does, there is a bug.
Edit History
It does not only "not store" the changes, but it deletes the content! If I there is some text in the content field, and then I store an update text, result is an empty content field. Thus it does write to the database. And why should it store the content in an other database filed than whit it belongs to? If it does, there is a bug.