[commits] Horde branch master updated. c6770ebd085b14e648132ae155fed28239f19a6e

[Michael J. Rubinsky]

The branch "master" has been updated.
The following is a summary of the commits.

from: da8065896cd0618dadf774164c3a9da41189de58

38bc207 Partially revert 4da58a51eb070909ec7fcccdf01c833992ea6851
c6770eb This method doesn't make much sense as implemented.

Summary: http://github.com/horde/horde/compare/da8065896cd0618dadf774164c3a9da41189de58...c6770ebd085b14e648132ae155fed28239f19a6e

-----------------------------------------------------------------------

commit 38bc2070e38318f97aad3c6298e88de7f00d4927
Author: Michael J Rubinsky <mrubinsk at horde.org>
Date:   Fri Nov 6 13:36:08 2015 -0500

    Partially revert 4da58a51eb070909ec7fcccdf01c833992ea6851
    
    This won't work as inteded, as both agendas AND alarms can set $user.
    This was causing non-admin users to have 'busy' appear as the alarm
    title in place of the actual event title.

 kronolith/lib/Event.php |   10 ++++------
 1 files changed, 4 insertions(+), 6 deletions(-)

http://github.com/horde/horde/commit/38bc2070e38318f97aad3c6298e88de7f00d4927

-----------------------------------------------------------------------

commit c6770ebd085b14e648132ae155fed28239f19a6e
Author: Michael J Rubinsky <mrubinsk at horde.org>
Date:   Fri Nov 6 13:50:01 2015 -0500

    This method doesn't make much sense as implemented.
    
    A "Private" event should *ONLY* be viewable by the event creator.
    That's why it's private. Allowing it to be shown to users with READ
    perms, even when generating alarms/agendas defeats this purpose. I.e.,
    any event with the private flag set will only ever be viewable by
    the creator. Even when generating agendas and alarms.

 kronolith/lib/Event.php |   14 +++-----------
 1 files changed, 3 insertions(+), 11 deletions(-)

http://github.com/horde/horde/commit/c6770ebd085b14e648132ae155fed28239f19a6e