~kubuntu-members/kdepimlibs/4.11 : changes

~kubuntu-members/kdepimlibs/4.11 » Changes from revision 13432

From Revision 13416 to 13397

Rev	Summary	Authors	Date
13416	Reduce nesting. Reduce nesting.	Sergio Martins	10 years ago
13415	Don't modify the event after the user canceling the modifica... Don't modify the event after the user canceling the modification. When the user gets asked "You're not the organizer, do you really want to edit?" we were ignoring the return value and modifying it anyway.	Sergio Martins	10 years ago
13414	Reduce nesting, having a hard time reading this... Reduce nesting, having a hard time reading this...	Sergio Martins	10 years ago
13413	Fix bug where we would send an e-mail with a forged From: Fix bug where we would send an e-mail with a forged From: This case happened when we were not the organizer and then modified the event. An e-mail would be sent with From: <organizer>, with all participants in CC. The correct is to not send anything, because the user was already warned via message boz that the event will become out of sync with the organizer's. BUG: 289533 BUG: 318394 FIXED-IN: 4.11.3	Sergio Martins	10 years ago
13412	sync the unit-tests with master. sync the unit-tests with master. This makes much easier to be able to commit in KDE/4.11 and merge to master. Otherwise I'd have to commit a fix in KDE/4.11 and then commit the unit test in master, since akonadi isolated tests don't run on KDE/4.11	Sergio Martins	10 years ago
13411	Don't send CANCEL to attendees when deleting an event we di... Don't send CANCEL to attendees when deleting an event we didn't organize. When deleting something that's not ours, only a REPLY with PartStat=Declined must be sent, and to the organizer only. Due to a bug, CANCEL was being sent to everybody, as if we were the organizer. Unit-test will go in master. Bug 318394 should be similar, but for modification instead of deletion. BUG: 217211 BUG: 306755 CCBUG: 318394 FIXED-IN: 4.11.3	Sergio Martins	10 years ago
13410	Wait for changes from resource to be written to Akonadi befo... Wait for changes from resource to be written to Akonadi before marking change as processed This fixes a problem with invalid RIDs after inter-resource moves. When there is an another changeReplay for the just moved item scheduled in the new parent resource, the item will have invalid RID (or rather RID assigned to it by the previous parent resource). It's because the ItemModifyJob dispatched from ResourceBase::changesCommitted() with the new RID is not finished yet when the next task is dispatched, and so the item in resource's EntityCache is not invalidated and the resource will use it instead of the updated one. By waiting for the ItemModifyJob dispatched from changesCommited() to finish before marking the change as processed and dispatching next task we make sure that in case the next task involves the same item the change will be stored in Akonadi and the item will be invalidated in local caches, forcing the resource to fetch the item again from Akonadi before starting the task. This fixes 'Invalid uidset' error reported by IMAP resources after the MailDispatcher agent moves the mail from local Outbox to remote Sent folder and updates it's flags. BUG: 323762 BUG: 324807 CCBUG: 314964 FIXED-IN: 4.11.3	Dan Vrátil	10 years ago
13409	Fixed METADATA support for the GetMetaDataJob. Fixed METADATA support for the GetMetaDataJob. REVIEW: 113481	Christian Mollekopf	10 years ago
13408	Support for counter-proposals is back for 4.11.3. Support for counter-proposals is back for 4.11.3. Since the akonadi port this has been broken.	Sergio Martins	10 years ago
13407	Fix save/load dialog size Fix save/load dialog size	Montel Laurent	10 years ago
13406	Don't crash when the counter proposal editor delegate is not... Don't crash when the counter proposal editor delegate is not set. Wasn't being initialized in the ctor.	Sergio Martins	10 years ago
13405	Don't show collection dialog when creating a recurring excep... Don't show collection dialog when creating a recurring exception. When accepting an invitation that has RECURRENCE-ID, don't ask in which collection to store the incidence in. Just use the same one as the main recurring series uses.	Sergio Martins	10 years ago
13404	Fix build. Fix build.	Sergio Martins	10 years ago
13403	Don't display "No recurrence" when it's a recurrence excepti... Don't display "No recurrence" when it's a recurrence exception. aka incidence with RECURRENCE-ID	Sergio Martins	10 years ago
13402	Fix accepting "cancel" messages with recurring id. Fix accepting "cancel" messages with recurring id. It was bailing out too early because it was looking for the exception which doesn't exist yet. Now it goes straight to Scheduler::acceptCancel(incidence) which has knowledge about recurring id, so it creates an exception with STATUS:CANCELED. unit-tests pass now	Sergio Martins	10 years ago
13401	Reset operation to none here, otherwise we can't call this t... Reset operation to none here, otherwise we can't call this twice.	Sergio Martins	10 years ago
13400	Fix crash detected in unit-tests. Fix crash detected in unit-tests.	Sergio Martins	10 years ago
13399	We now support accepting method=CANCEL with RECURENCE-ID. We now support accepting method=CANCEL with RECURENCE-ID. Which means if you receive an invitation CANCEL for an individual recurrence occurrence kontact won't delete your whole recurrence series. Unit test following. BUG: 279300	Sergio Martins	10 years ago
13398	Don't create translated special collection otherwise it will... Don't create translated special collection otherwise it will create on disk translated folder not very good but the real bug is that it will try to create 2 "inbox" one translater another inbox in C language. => it will crash at the beginning and will create bug reported where kmail doesn't start because there is 2 inbox. We have a function which change displayname so not necessary to create theses folders as translated. Tested and it works better :)	Montel Laurent	10 years ago
13397	More cleanup. More cleanup.	Sergio Martins	10 years ago

Older »