| Summary | Error with non existing default identities |
| Queue | IMP |
| Queue Version | Git master |
| Type | Bug |
| State | Not A Bug |
| Priority | 1. Low |
| Owners | |
| Requester | o+horde (at) immerda (dot) ch |
| Created | 09/17/2012 (4673 days ago) |
| Due | |
| Updated | 09/24/2012 (4666 days ago) |
| Assigned | 09/23/2012 (4667 days ago) |
| Resolved | 09/24/2012 (4666 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
problem is caused by anything Horde has done. Unless it can be
shown how/why Horde caused this problem, we are not going to put in
fixes.
but indeed i can confirm that the current stable horde does update the
default_identity when it gets deleted. so it must have been an issue
with an earlier version, or with the migration from horde3.
i guess you can close the ticket, we just fixed the affected profiles
in the database.
State ⇒ Feedback
Priority ⇒ 1. Low
problem is caused by anything Horde has done. Unless it can be shown
how/why Horde caused this problem, we are not going to put in fixes.
justification for high: users affected by this problem cannot reply to
an email
Priority ⇒ 3. High
Type ⇒ Bug
Summary ⇒ Error with non existing default identities
Queue ⇒ IMP
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
which do no longer exist anymore. We have not investigated whether
this is a legacy issue, or still happening when deleting the default
identity.
Please merge our mitigation:
/imp/lib/Prefs/Identity.php
329,331c329,333
< $tmp = $ids[$default];
< unset($ids[$default]);
< $ids[$default] = $tmp;
---
$tmp = $ids[$default];
unset($ids[$default]);
$ids[$default] = $tmp;
}