Closed Bug 323011 Opened 18 years ago Closed 16 years ago
Unifinder default option should not be 'all events'
Apparently, we managed to take down a caldav server by running it out of memory. We ran a caldav query for all events, and the server died trying to create a report for 2 years worth of events in a very dense calendar. I was asked to consider at least making this a non-default option (especially since we query at startup). Filing as UNCO, though, since I'm not sure if it's something we really want to do.
Reassigning all automatically assigned bugs from Mostafa to firstname.lastname@example.org Bugspam filter: TorontoMostafaMove
Assignee: mostafah → nobody
I would like to second this. Networked providers that do not download all events anyway (as webdav does), should not start out with getting all events from the network. This for example applies to the upcoming google calendar provider.
Unifinder is also available in Lightning now.
Component: Sunbird Only → General
QA Contact: sunbird → general
Version: Trunk → unspecified
The patch for this should be easy enough. The question is, what should the new default be. Christian, any opinions on this?
I'd vote for "Events in the Next 7 Days".
I vote for "Today's Events".
This patch makes the default "Next 7 Days".
Assignee: nobody → philipp
Status: NEW → ASSIGNED
Attachment #295920 - Flags: review?(daniel.boelzle)
Comment on attachment 295920 [details] [diff] [review] Set default value to 'next 7 days' r=dbo; "next 7 days" has been agreed with Christian, setting ui+.
Checked in on HEAD and MOZILLA_1_8_BRANCH -> FIXED
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Target Milestone: --- → 0.8
Verified in Lightning (build 2008010904) and Sunbird (build 2080109) -> task is fixed.
Status: RESOLVED → VERIFIED
Sorry, I do not believe it is fixed. The unifinder is unable to "find events" when I'm looking right at them in the calendar. (I'm using the latest SB and Ltng nightlies.)
Tx, ssitter. I did not realize it was a separate bug.
You need to log in before you can comment on or make changes to this bug.