[kronolith] Default external calendar
Gerard Breiner
gerard.breiner at ias.u-psud.fr
Fri Mar 16 15:16:51 UTC 2012
Le 14/02/2012 15:37, Jan Schneider a écrit :
>
> Zitat von Martin Hochreiter <linuxbox at wavenet.at>:
>
>>> You cannot simply replace strings in the value copied from the
>>> database, because it is a serialized hash. Using $registry in
>>> prefs.local.php is not a good idea either.
>>> Instead you should create a preference hook that builds the hash,
>>> and return it serialized.
>>>
>> what a pitty :) ... ok, thank you I will create a hook for that (new
>> world for me...)
>> What should I use instead of the $registry variable to get the
>> credentials - or is it ok
>> to use it in the hooks?
>
> The prefs_init hook already gets the user name passed.
>
Hello ,
I'm working on this too... So I followed the above Jan's advice and as
well as read the very good doc /horde/config/hooks.php.dist (many thanks
for all the work). The result is that I managed to create the remote
calendar by working with prefs and hooks.local.php.
Here is what I've done :
kronolit/config/prefs.local.php
[CODE]
// remote calendars
$_prefs['remote_cals'] = array(
'value' => '',
'hook' => 'true',
'locked' => 'false'
);
[/CODE]
[CODE]
kronolith/config/hooks.local.phpclass Kronolith_Hooks
{
public function prefs_init($prefs, $value, $username, $scope_ob)
{
switch ($prefs) {
case 'remote_cals':
$no_serialize = array(array('name'=>'Calendar',
'url'=>'https://myurl/caldav.php/' .$username. '/agenda',
'user'=> $username
// 'password' => $password
)
);
$value = serialize($no_serialize);
return $value;
}
}
}
[/CODE]
Nevertheless at this time I don't know how to catch the password... If
Jan look at this again I would appreciate a little more hints about this
last issue.
Best regards
Gerard Breiner
More information about the kronolith
mailing list