| Summary | Change default IMAP factory return after authentication |
| Queue | IMP |
| Queue Version | Git master |
| Type | Enhancement |
| State | Resolved |
| Priority | 1. Low |
| Owners | slusarz (at) horde (dot) org |
| Requester | leena.heino (at) uta (dot) fi |
| Created | 11/28/2012 (4601 days ago) |
| Due | |
| Updated | 11/29/2012 (4600 days ago) |
| Assigned | 11/29/2012 (4600 days ago) |
| Resolved | 11/29/2012 (4600 days ago) |
| Milestone | |
| Patch | No |
State ⇒ Resolved
commit 7668de8e3f35fb148232a294f5c2041eda543dde
Author: Michael M Slusarz <slusarz@horde.org>
Date: Thu Nov 29 13:27:54 2012 -0700
Request #11774: Change default IMAP object returned by factoryupon successful authentication
No changelog for this
imp/lib/Auth.php | 4 ++-
imp/lib/Factory/Imap.php | 51 +++++++++++++++++++++++++++++++++++----------
2 files changed, 42 insertions(+), 13 deletions(-)
http://git.horde.org/horde-git/-/commit/7668de8e3f35fb148232a294f5c2041eda543dde
Type ⇒ Enhancement
State ⇒ Assigned
Priority ⇒ 1. Low
wiki works on accident, because of incorrect H4 session/auth
bootstrapping code.
In H5, the authenticated imap object *is* available: you just need to
know the exact server ID used to authenticate.
Assigned to Michael Slusarz
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ IMP_Factory_Imap -> create() regression
Queue ⇒ IMP
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
getInstance('IMP_Factory_Imap') -> create() is called from Horde's hooks it
behaves differently in IMP 5 than it does in IMP 6. In IMP 5 the create()
call populates the newly created IMP_Imap object, where as the
create() call in IMP 6 leaves the newly created IMP_Imap object
unpopulated and null.
Because of this change in the behavior of create() call the adding of
realm to userid as documented in the wiki article will not work in IMP
6: http://wiki.horde.org/ImpH4Realm