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

noreply at bugs.horde.org noreply at bugs.horde.org
Tue Mar 12 13:56:55 UTC 2013


Ticket-URL: http://bugs.horde.org/ticket/11738
  Ticket           | 11738
  Aktualisiert Von | t.nintemann at medial-networks.de
  Zusammenfassung  | Revamped kolab-webmail bundle for H5
  Warteschlange    | Kolab
  Typ              | Enhancement
  Status           | Feedback
  Priorität        | 2. Medium
  Milestone        |
  Patch            |
  Zuständige       |
+Neue Anlage      | kolab_webmail-h5.patch

t.nintemann at medial-networks.de (2013-03-12 13:56) hat geschrieben:

Hi List,

i was playing around with horde 5 on Kolab and i saw this Bug-entry.
i have made an new Patch that works to me perfectly on Horde-5.0.4.

The only problem was in the conf.php which is created by kolab-webmail.
There  are  some Horde Tables that are not automatically created in SQL.

horde.alarms, horde.perms and horde.token will not created.
If i comment out this Horde DB Definitions in conf.php, everything works fine.

Next i found, was that when i activate Active Sync in Horde, the  
horde.active-sync Table is not created,
It seems that Horde with Kolab enabled did not create missing Tables in SQL.
Is it possible to create DB Tables per hand?

Thanks for the Work....



>>>> - Why did you remove the mbox_icon and display_folder hooks?
>>> Do you see this as unresolved? I have not received any response to my
>>> comments and was not able to resolve the issue myself.
>>> I just retested, when activating the mbox_icon hook the folder list
>>> on the left no longer loads in IMP, but despite DEBUG logging I
>>> couldn't spot obvious error messages. It's sufficient to have the
>>> code in hooks.php, even when not activated in imp/conf.d.
>> You mentioned fatal errors earlier in the ticket, but I didn't see a
>> bug report or more detailed information about those anywhere. If they
>> don't work, they need fixing, not disabling.
> This ticket is about code specific to the kolab package, the code in  
> question no longer works with the new version, I reported the  
> problem and suggested a solution (code removal) - I didn't see the  
> need for a separate ticket.
> Lacking a response telling me differently, I assume that that the  
> code is based on functionality no longer available in the current  
> version of Horde. As nobody besides me seems to miss Kolab  
> integration at all, removing eye candy shouldn't be a problem at all.

t.nintemann at medial-networks.de (2013-03-12 13:56) hat hochgeladen:  


More information about the bugs mailing list