Re: CalDav and invitation duplicates

This is a multi-part message in MIME format.
--------------4AD454345B1CD7075762BF8A
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable


Am 04.09.19 um 18:49 schrieb Michael J Rubinsky:
>
> Quoting Markus Bozem <[email protected]>:
>
>>>
>>> Hi Markus,
>>>
>>> I had the same problem.=A0 If you can't wait for the patch, you can=A0=

>>> always manually disable Kronolith generation of notifications by=A0
>>> updating /horde/kronolith/lib/Kronolith.php=A0 until the fix is=A0
>>> available mainstream.=A0 I did so by inserting a 'return' just before=

>>> =A0the section that sends the itip notifications.
>>>
>>> Aria
>>> -- kronolith mailing list
>>> Frequently Asked Questions: http://wiki.horde.org/FAQ
>>> To unsubscribe, mail: [email protected]
>>
>> Hi Aria,
>>
>> thank you for this hint.
>>
>> To all interested persons:
>>
>> return was inserted here:
>>
>> =A0=A0=A0 static public function sendITipNotifications(
>> =A0=A0=A0=A0=A0=A0=A0 Kronolith_Event $event, Horde_Notification_Handl=
er
>> $notification,
>> =A0=A0=A0=A0=A0=A0=A0 $action, Horde_Date $instance =3D null, $range =3D=
 null, array
>> $cancellations =3D array())
>> =A0=A0=A0 {
>> =A0=A0=A0=A0=A0=A0=A0 global $injector, $registry;
>>
>> =A0=A0=A0=A0=A0=A0=A0 return;
>>
>> =A0=A0=A0=A0=A0=A0=A0 if (!$event->attendees) {
>> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 return;
>> =A0=A0=A0=A0=A0=A0=A0 }
>>
>>
>> This solution works ok:
>> Active Sync can still be used to send invitations. (iPhone tested)
>> When meeting is created in kronolith - webfronted invitations are not
>> send. (not used here)
>> Only problem when using CalDAV -> when accepting invitations the
>> external organizer will be replaced with the accepting person.
>> (tolerable)
>>
>> To the maintainers:
>>
>> But this is only a workaround. And the patch for an user option is in
>> master branch since 2015.
>
> Correct. Along with major changes to how invitations work at the core.
>
>
>> So what is the problem in integrating this (small) patch for a big
>> problem into stable?
>
> If you are referring to just the user preference; that's technically a
> new feature, so must wait until a feature release, not a bug fix/"dot"
> release. This is why it's in the master branch, and not FRAMEWORK_5_*
>
>> Time to do it?
>
> A major factor, yes. There are major architectural changes in place in
> our entire development and release toolchain. We are also retooling to
> use a distribution channel other than PEAR for our next major
> releases. This takes time, and if I'm honest, more man hours than we
> have at our disposal at the moment.
>
>> Should I create a push reguest?
>
> Wouldn't help, it's already in the code base for the release where it
> will be available.
>
>> Can I help in an other way?
>
> Sure! You can join the [email protected] mailing list and help with
> tasks we still have open for our major release.
>
>> Are there other concerns integrating this patch?
>> Is this project death?
>
> Sometimes it seems so, but I assure you we are alive and well :)
>
>> Markus.
>
As for the non-pear stuff, i've been blocked a little lately but it's
being tested / used meanwhile and will find it's way into upstream. Sorry=
 :(


>
>
>
--=20
Ralf Lang
Linux Consultant / Developer
Tel.: +49-170-6381563
Mail: [email protected]
B1 Systems GmbH
Osterfeldstra=DFe 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537


--------------4AD454345B1CD7075762BF8A
Content-Type: application/pgp-keys;
 name="pEpkey.asc"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
 filename="pEpkey.asc"

-----BEGIN PGP PUBLIC KEY BLOCK-----

mQENBFuk7+4BCAC00ahJdTHyZEiAxFB89Bi6HuusvcIErw1Pi2xHMR06KQsVGIBw
fr9IcdlHSldIYrcMVvK3FRMZs3A5WJEyR3vwapNOM6W3PomkiIIF9gtWFHIHemQo
bgT9bq3pCwePfWyBpa1BazoXYHxKaWIQPmMIvUYo5nThhpnFrtg+Y7C/YR7mhlp+
HfFGyGgMMi7NvwK2Nb/VXbEttkc24Y8fWytf/x2Or2hKhrWDscjSmXndCEuJRher
qgccFzcM7haiJtwqlprygZk+M1dxrb3257Kopa9Jg4hquaj0dabb54Rybh3Zs4Ze
BOFWRb2eJRAhO0livTVCPr2v3poenH8TKnaXABEBAAG0HlJhbGYgTGFuZyA8bGFu
Z0BiMS1zeXN0ZW1zLmRlPokBVAQTAQgAPhYhBNC/U52ImXHKvyQM8dL/BSw1UJap
BQJbpO/vAhsDBQkB4TOABQsJCAcCBhUKCQgLAgQWAgMBAh4BAheAAAoJENL/BSw1
UJapVFgH/3qsTKmlJjZ6lGjueyR9Ph/Y9VXe2LBTAKNcCrGjHnHVMt7LKW/UuK2Q
E53IaK7CYy+odDmxYECsGw5X+O100ofjJFUy2HtI6eOAGprOmuN6V1FEaCGFt7E2
n+pOuj64QSnzhDs18viNnsdRqTq5RhmEGgRVenhONQTLGwVUec+zuF9HRcLKg5yI
mtiWSIxwC96pFGv95Es/jwh0f1wJmChkshWuJ3mr4UfvAb2BXbqpuwH9hA0hAOmY
0S5cGrP47xyuptfXG4NRHjEAQLPHbQgYM8/F63JRa6xyzoVmg+/d/iGvHAhCsXun
E/mHU67I3FbFn8iCkG9Ynbk0choGQbO5AQ0EW6Tv7wEIAOLRI56sjrRA0VTA3zZG
8JB+7otYarCbK4GBS2U8w4uxB/1PizmE4z5y5QTWAvml6du5I1GE4kDU6WeqLaxi
Sv6DaoDUZIIMWaVBpW6jb3yyQzoYWu2ap6aZRY3Xpnyvo/Y+pCQjkkzZp3Kg9uD+
fM64sl2lznuXZAJquExHqW69POh5HLNyMXj0O5erDn9gaI1hjcI2KzSkuzFW5W3V
flYLG+BdDcdbH1Lh8jNQ9SEqTsWdvDF9NfVJuTugg+i0ZunD9nW2JIClMjDW8WT0
IYAK/jNxWJeEvLtTuc7WORwm47tx2qH5LlzbzUfPI6gBvjvvSFYWa/6jU5bYZFN2
tD0AEQEAAYkBPAQYAQgAJhYhBNC/U52ImXHKvyQM8dL/BSw1UJapBQJbpO/vAhsM
BQkB4TOAAAoJENL/BSw1UJapc90IAICy3CJv9IKbOasaEHS4OwodjHE8otTBdZh3
+TbkoJli/EW7oYCoidxAhdzETFqDC48ppZdg9LUf5IJhtHO8AFIMwhcQR8EfSWFl
QemBQhdxxWqWNpiA0+z9gqrI0CTuXsrt617FMMi70yeUrdC59t1qNzxedOYF902J
UtetYafqsSf4T5rUDUft4A0wybSEnmCe0f+NN/PVgDAapunbyPulHyh52MkST7+H
rj2CjwBJbtSB06nNafvZaF7l9pE2GK0hawQxRFfKDNvY1/txuwBIRTsmFy5txLfW
3NaLZJGJXN3g1G7ozRfejWizyVCkYkTHk1h7s1hV+Ml1lZ1ivQk=3D
=3DUgyR
-----END PGP PUBLIC KEY BLOCK-----

--------------4AD454345B1CD7075762BF8A
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-- 
kronolith mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: [email protected]

--------------4AD454345B1CD7075762BF8A--