[Tickets #14259] Re: Event notification from another user's private calendar
noreply at bugs.horde.org
noreply at bugs.horde.org
Thu Feb 18 15:35:18 UTC 2016
DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.
Ticket URL: https://bugs.horde.org/ticket/14259
------------------------------------------------------------------------------
Ticket | 14259
Updated By | lfbm.andamentos at gmail.com
Summary | Event notification from another user's private calendar
Queue | Kronolith
Version | 4.2.14
Type | Bug
State | Unconfirmed
Priority | 1. Low
Milestone |
Patch |
Owners |
+New Attachment | horde_debug.txt
------------------------------------------------------------------------------
lfbm.andamentos at gmail.com (2016-02-18 15:35) wrote:
I´ve have inserted in Horde/Alarm.php the following debug commands
below line 116:
$alarms = $this->_list($user, $time);
Horde::debug($user);
Horde::debug($time);
Horde::debug($alarms);
Then I ran horde-alarms.php.
Then I could spot the event from another user´s private calendar being
pulled. Please see the attached horde_debug.txt.
The problem is the event with id 'DO9fBDwIcfYXXR3jXH-yy6U' was pulled
for display to the user 'lfbm', but actually this event belongs to a
calendar which this user ('lfbm') does not have access to.
> array(10) {
> ["id"]=>
> string(54) "20160118162443.oZDEk8Q8YkKsCOTBqqjqW40 at marzagao.com.br"
> ["user"]=>
> string(4) "lfbm"
> ["start"]=>
> object(Horde_Date)#780 (9) {
> ["_year":protected]=>
> int(2016)
> ["_month":protected]=>
> int(2)
> ["_mday":protected]=>
> int(18)
> ["_hour":protected]=>
> int(13)
> ["_min":protected]=>
> int(30)
> ["_sec":protected]=>
> int(0)
> ["_timezone":protected]=>
> string(3) "UTC"
> ["_defaultFormat":protected]=>
> string(11) "Y-m-d H:i:s"
> ["_formatCache":protected]=>
> array(0) {
> }
> }
> ["end"]=>
> object(Horde_Date)#747 (9) {
> ["_year":protected]=>
> int(2016)
> ["_month":protected]=>
> int(2)
> ["_mday":protected]=>
> int(18)
> ["_hour":protected]=>
> int(15)
> ["_min":protected]=>
> int(0)
> ["_sec":protected]=>
> int(0)
> ["_timezone":protected]=>
> string(3) "UTC"
> ["_defaultFormat":protected]=>
> string(11) "Y-m-d H:i:s"
> ["_formatCache":protected]=>
> array(0) {
> }
> }
> ["methods"]=>
> array(1) {
> [0]=>
> string(6) "notify"
> }
> ["params"]=>
> array(1) {
> ["notify"]=>
> array(5) {
> ["__desc"]=>
> string(0) ""
> ["sound"]=>
> string(0) ""
> ["show"]=>
> array(3) {
> ["__app"]=>
> string(9) "kronolith"
> ["event"]=>
> string(23) "DO9fBDwIcfYXXR3jXH-yy6U"
> ["calendar"]=>
> int(0)
> }
> ["ajax"]=>
> string(49) "event:internal|0:DO9fBDwIcfYXXR3jXH-yy6U:20160218"
> ["subtitle"]=>
> string(113) "De <strong>quinta, 18 fevereiro 2016 às
> 12:00</strong> até <strong>quinta, 18 fevereiro 2016 às
> 13:00</strong>"
> }
> }
> ["title"]=>
> string(25) "estréia vikings season 4"
> ["text"]=>
> NULL
> ["snooze"]=>
> NULL
> ["internal"]=>
> NULL
> }
In the attached slq queries you can see the event
'DO9fBDwIcfYXXR3jXH-yy6U' belongs to the calendar 'robm', which is the
private calendar for another user (the user 'robm'). Please see the
attached PDFs.
I hope it helps debuging the problem.
lfbm.andamentos at gmail.com (2016-02-18 15:35) uploaded: horde_debug.txt
https://bugs.horde.org/h/services/download/?app=whups&actionID=download_file&file=horde_debug.txt&ticket=14259&fn=%2Fhorde_debug.txt
More information about the bugs
mailing list