| Summary | horde's config/hooks.php gives kolab examples that use deprecated method calls |
| Queue | Kolab |
| Type | Bug |
| State | Resolved |
| Priority | 1. Low |
| Owners | jan (at) horde (dot) org, wrobel (at) horde (dot) org |
| Requester | m.gabriel (at) das-netzwerkteam (dot) de |
| Created | 12/24/2007 (6474 days ago) |
| Due | |
| Updated | 02/29/2008 (6407 days ago) |
| Assigned | 02/25/2008 (6411 days ago) |
| Resolved | 02/29/2008 (6407 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
Taken from Chuck Hagenbuch
State ⇒ Resolved
Assigned to Chuck Hagenbuch
Assigned to Jan Schneider
Taken from Gunnar Wrobel
New Attachment: HK-GW-Deprecated_hooks.patch
In the old driver version the whole share management wasn't integrated
into the main share driver. So the Kolab module had to synchronize
after any change. This was pretty fragile and was one of the central
fixes in the newer driver versions.
@Chuck or Jan: Can you commit the attached patch? Thanks!
Queue ⇒ Kolab
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ horde's config/hooks.php gives kolab examples that use deprecated method calls
Queue ⇒ Horde Groupware Webmail Edition
State ⇒ Unconfirmed
in horde's config/hooks.php you find these hook examples (commented
out), that still use updateShare, removeShare of horde 3.1.x (i guess).
if (!function_exists('_horde_hook_share_add')) {
function _horde_hook_share_add(&$share)
{
require_once 'Horde/Kolab.php';
return Kolab::updateShare($share);
}
}
if (!function_exists('_horde_hook_share_modify')) {
function _horde_hook_share_modify(&$share)
{
require_once 'Horde/Kolab.php';
return Kolab::updateShare($share);
}
}
if (!function_exists('_horde_hook_share_remove')) {
function _horde_hook_share_remove(&$share)
{
require_once 'Horde/Kolab.php';
return Kolab::removeShare($share);
}
}
what exactly was the meaning of these hooks? are they still needed in
horde-3.2.x and if yes, how can i substitute them?
best,
mike