Bug 352091 - CalDAV events three months ago or older are not downloaded
Summary: CalDAV events three months ago or older are not downloaded
Status: RESOLVED DUPLICATE of bug 339449
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-09-01 10:28 UTC by sparhawk
Modified: 2015-09-01 14:28 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description sparhawk 2015-09-01 10:28:00 UTC 
I'm using KOrganizer 4.14.10, which doesn't appear in the drop-down menu to select the version.

I set KOrganizer to sync with my CalDAV (Owncloud) instance. However, any event three months ago or older is not synced. Further, KOrganizer dynamically removes events from three months ago or older, as time progresses. I often need to check events prior to then, so this syncing is essential for my calendar application. Lighting/Thunderbird works perfectly well with this.

Reproducible: Always

Steps to Reproduce:
1. Sync KOrganizer with CalDAV.
2. Look at events three months or older.

Actual Results:  
With the exception of repeating event, there are no events there.

Expected Results:  
All events should be present.

I'm using Arch Linux, with KOrganizer installed from the official packages.
Comment 1 Allen Winter 2015-09-01 13:10:36 UTC 
probably this belongs to Greg and the Akonadi product.
Comment 2 sparhawk 2015-09-01 13:14:05 UTC 
Thanks, I wasn't exactly sure how to file it. I had set up the sync via the "Calendars" settings in KOrganizer.
Comment 3 Grégory Oestreicher 2015-09-01 13:16:29 UTC 
Indeed, thanks. It'll be configurable with the next stable release, 15.12.

*** This bug has been marked as a duplicate of bug 339449 ***
Comment 4 sparhawk 2015-09-01 13:24:45 UTC 
Thanks for that, and apologies for not finding the original bug.
Comment 5 Grégory Oestreicher 2015-09-01 14:28:43 UTC 
No need to apologize, the original bug being closed it will not show up by default :)

Thanks for reporting the issues you find,
Grégory