Uh oh!
There was an error while loading. Please reload this page.
send invitations for shared calendars - #9609
Conversation
17fdafd to
95165f9Comparegeorgehrke
commented
May 25, 2018
note to myself: Can this solution cause issues with infinite invitation loops? Should the address list only be limited to the current user accessing it and not to all users possibly having access to it? |
georgehrke
commented
May 25, 2018
Possibly
Yes, just replace |
georgehrke
commented
May 25, 2018
Saved this patch as a gist because I might need the Principal changes for future work: https://gist.github.com/georgehrke/ce704d4370b8e9d60231f2ea35d15f0c |
95165f9 to
b11a043CompareCodecov Report
@@ Coverage Diff @@## master #9609 +/- ##
============================================
- Coverage 51.15% 2.07% -49.09% - Complexity 25692 25697 +5
============================================
Files 1568 1568 Lines 88039 88052 +13 ============================================
- Hits 45036 1824 -43212 - Misses 43003 86228 +43225
|
Signed-off-by: Georg Ehrke <developer@georgehrke.com>
b11a043 to
a9c313cComparegeorgehrke
commented
May 25, 2018
In contrast to the previous patch this doesn't check whether the current user is a rw-share, but then a person with a ro-share should not be able to update calendar objects and trigger the |
| $oldObj = null; | ||
| } | ||
| $this->processICalendarChange($oldObj, $vCal, $addresses, [], $modified); |
There was a problem hiding this comment.
if new participant addresses don't have an e-mail set does this do 💥 ?
There was a problem hiding this comment.
No, this is properly handled by processICalendarChange.
As I said in the methods comment, this is basically just a copy of parent:: calendarObjectChange, i just replaced line 133. That's why I also didn't write tests 🙈
rullzer
commented
May 30, 2018
Tests would be appreciated as this is something we might else easily break in the future |
MorrisJobke
commented
May 22, 2019
Reverted in #15676 |
fixes#3830