Ticket 583 was not found.
[#4871] Nag requires an owner attribute on tasks
| Summary | Nag requires an owner attribute on tasks |
| Queue | Nag |
| Queue Version | HEAD |
| Type | Bug |
| State | Resolved |
| Priority | 1. Low |
| Owners | |
| Requester | wrobel (at) pardus (dot) de |
| Created | 1/11/07 (7107 days ago) |
| Due | |
| Updated | 1/12/07 (7106 days ago) |
| Assigned | 1/11/07 (7107 days ago) |
| Resolved | 1/12/07 (7106 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
History
State ⇒ Resolved
'owner' => Auth::getAuth(),
in _buildTask() in Nag_Driver_kolab?
be nice if you could change that. Thanks!
State ⇒ Feedback
'owner' => Auth::getAuth(),
in _buildTask() in Nag_Driver_kolab?
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ Nag requires an owner attribute on tasks
Queue ⇒ Nag
New Attachment: nag_lib_Driver_kolab.php-empty_owner_fixes-20070111.patch
State ⇒ Unconfirmed
does not.
I would like to look deeper into the Kolab Object Format to decide how
this attibute should be handled. Otherwise there might be conflicts
with other mail clients accessing the same Task Objects. So I did not
add this attribute to the kolab driver yet.
Now I fixed nag to accept an empty owner attribute though I am not
certain whether that is ok. If you feel that it would be better to
require each driver to support the owner attribute then I would try to
add that sooner.
Suggested patch attached.