Actions
Patch #12659
closedBroken dirty_tracking inside a after_save callback for the Issue model due to reload in Mailer
Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Issues
Target version:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Description
.reload not just gives us current record from database, but also resets *_changed? .changes and etc. in all later methods from callback chain for the reloaded item as a side-effect.
Since there are many plugins which rely on callbacks and sometimes dirty-tracking, this is a problem.
For now, there is a workaround - we can save .changed data in before_save callback. But i think it is better to just isolate the issue record in mailer.
Files
Actions