[Tickets #14259] Re: Event notification from another user's private calendar

noreply at bugs.horde.org noreply at bugs.horde.org
Fri Feb 19 03:08:25 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              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


lfbm.andamentos at gmail.com (2016-02-19 03:08) wrote:

Okay, I just realized my table kronolith_sharesng_users had two problems:


1 - One row had a share_id which did not existed on kronolith_sharesng  
table, but referring to a user_uid that did exist on  
kronolith_sharesng (which, in the case, was my uid: 'lfbm')

So it was really messing up the $shares variable from line 310 from  
file Horde/Share/Sql.php, since it does not verify if the share_id  
from kronolith_sharesng_users exists on kronolith_sharesng.

The outcome is $shares array ends up with one last item that only has  
perms, but not a share_id, share_name and so on.


2 - One share_id that exists (and is used by a active user) on  
kronolith_sharesng did not existed on kronolith_sharesng_users. I'm  
not sure what was the effect it was causing (if any at all).


So after adjusting number 1 above, horde-alarms has stopped  
duplicating entries with the wrong user_uid.

As for number 2, I'm not sure yet if this will have any effect.

As for why the share_id got messed up on kronolith_sharesng_users, I  
think I'll never know. Maybe it was during db migration process. Can't  
say.

Anyway, I think this is not a bug, maybe the need for an enhancement,  
if at all, in order to add some verification code to see if  
$row['share_id'] actually exist on $shares before creating another  
array element in it on line 310 from Horde/Share/Sql.php.

Thanks!







More information about the bugs mailing list