Tickets :: Comment on [#11738] Revamped kolab-webmail bundle for H5

* Your Email Address
* Spam protection	Enter the letters below: . ,.__..__ .___. \./ \| \|\| \[__ \| \| \|__\\|__/[___\|___
Comment	>>> bundle/kolab-webmail needed some work-over to cope with H5. >>> >>> An open issue remains: How do I (in Bundle.php) read in a password >>> without console echo? It can be done, ConfigDb() does it somehow... >> >> http://dev.horde.org/api/master/lib/Cli/classes/Horde_Cli.html#method_passwordPrompt > > Thanks, I'll rework the code to include this. > >>> This patch, together with the one from bug #11737, give me a mostly >>> usable system with working Kolab integration. >> >> Looks mostly good. >> - Why does >> $GLOBALS['injector']->getInstance('Horde_Kolab_Session')->getImapServer() >> not work? > > You tell me... when I tested my configuration, access to the IMAP > server only worked after I (originally hard-coded) the server value > in that config file. This was way before I started changing real code > or creating bugs, so it may be different with the current > implementation (bug #11737). > >> - Why did you remove the mbox_icon and display_folder hooks? > > Because I got fatal PHP errors when the code tries to access > $types = > $GLOBALS['injector']->getInstance('Horde_Kolab_Storage')->getList()->listFolderTypes(); > > IIRC it was "listFolderTypes()" that was reported as unknown as a > member method. > >> - Use can use $kolabhost as the default value for the $smtphost and >> $ldaphost prompts. > > Thanks to the above documentation link I can now implement this. > >> - Why are the $vars->ldap__* setters necessary? > > Those were the values I seem to have to set in consequence of the > changes in bug #11737. Do you see a different way to handle this? My > insight into Horde's handling of IMAP server settings is still very > limited, and I rather suspect that setting "kolab__imap*" is now > obsolete...
Attachment
Watch this ticket

Saved Queries