View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
0001660 | v3.5 Release (Development) | [All Projects] General | public | 2015-08-09 03:40 | 2019-01-01 16:15 | ||||||||
Reporter | opto | ||||||||||||
Assigned To | |||||||||||||
Priority | high | Severity | major | Reproducibility | always | ||||||||
Status | new | Resolution | open | ||||||||||
Summary | 0001660: hooks in bulktasks: parent hook is not called | ||||||||||||
Description | on store, parent_id is never set for top Level Tasks because: bulktasks::postStore hook does not call parent hook. For all the other hooks, the parent (Tasks) hook is executed because the function is not present in bulktasks. This hook exists, does nothing but in my opinioun should call Tasks::postStore hook. seeing this: if (!$this->importing_tasks) { in Tasks postStore hook, it is probably meant to be called, although we don't Need most of what is done in there for importing. currently, we also don't call all parent postStore hooks probably the same for delete hook | ||||||||||||
Tags | No tags attached. | ||||||||||||
Attached Files |
|
![]() |
|
opto (manager) 2015-08-09 07:44 |
it seems intentional that CTask::postStore hook is not called, but: should the baseclass hook be called instead of doing nothing? the Task postStore hook does this as well. There could be oher Tasks in there that we Need to call, even if we don't want the Actions of the Task postStore |
![]() |
|||
Date Modified | Username | Field | Change |
---|---|---|---|
2015-08-09 03:40 | opto | New Issue | |
2015-08-09 03:41 | opto | Description Updated | View Revisions |
2015-08-09 03:55 | opto | Description Updated | View Revisions |
2015-08-09 04:02 | opto | Summary | hooks in bulktasks => hooks in bulktasks: parent hook is not called |
2015-08-09 07:44 | opto | Note Added: 0003756 | |
2016-12-26 23:34 | caseydk | Project | v3.3 Release => v3.4 Release (Current) |
2016-12-31 01:00 | caseydk | Priority | normal => high |
2019-01-01 16:15 | caseydk | Project | v3.4 Release (Current) => v3.5 Release (Development) |
2019-01-01 16:15 | caseydk | Category | Tasks => General |