Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Collaboration Suite > Users

Welcome to the Zimbra :: Forums!
Welcome, if you would like to post a comment please register. We also encourage you to explore all things Zimbra with our team and members of the community.

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 07-06-2008, 02:28 AM
Junior Member
 
Posts: 6
Default Recurring events with no end date last "only" 30 years

Hello!
I just switched to Zimbra and was quite surprised to see that my normal way of keeping track of birthdays does not work the way I was used to in other programs.

I normally store birthdays as yearly recurring events without an end date in my calender. As start day I use day the person was born including the right year in order to recognise "round" birthdays. Because many of my friends are above 30 this does not work in Zimbra out of the box. Even setting 100 yearly occurences does not work. It stops after 30 years.

Is there a way to change this behavior?

Otherwise I would set every birthday starting in the year 2000 an keep track of the real year in the contacts field tough this is not perfect for families where I normally store only a family contact. Doing it like this would force me to have a contact for each familiy member including children.

Greetings,
Carsten
__________________
ZCS 5.0.6 CE on Linux VServer with Ubuntu 8.04 Hardy Heron behind NAT and using a RelayHost
Reply With Quote
  #2 (permalink)  
Old 07-06-2008, 04:46 PM
Moderator
 
Posts: 6,237
Default

Sounds like Bug 28618 - Birthday events are synchronized only for persons under 30 years old

This one is reported solved in 5.0.7 Bug 28860 - Birthday appointmens before 197x

I get a slightly different result, no one can be older than 100

In the AJAX web-client create appointments (time or all day) & recurring every year (even created some around epoch to be sure) using july 6th - the start dates:
1950
1960
1969
1970
1971
1980
1990
1999
2000
2001

navigate to server.domain.com/zimbra/h/calendar?view=month&date=20080706
(or server.domain.com/zimbra/?app=calendar&view=week&date=20080706 but it's much easier to use HTML client as it loads faster)

navigate to 20080706 - all fine
navigate to 20500706 - all fine
navigate to 20510706 - missing 1950
navigate to 20610706 - missing 1950, 1960
navigate to 20710706 - missing 1950, 1960, 1969, 1970
navigate to 20810706 - missing 1950, 1960, 1969, 1970, 1971, 1980,
navigate to 20910706 - missing 1950, 1960, 1969, 1970, 1971, 1980, 1990
navigate to 21010706 - missing 1950, 1960, 1969, 1970, 1971, 1980, 1990, 1999
navigate to 21010706 - missing 1950, 1960, 1969, 1970, 1971, 1980, 1990, 1999, 2000

I noted it in bug 28618.
Reply With Quote
  #3 (permalink)  
Old 07-06-2008, 04:53 PM
Moderator
 
Posts: 6,237
Default

You might also want to vote for this RFE: Bug 11575 - Create an appointment when user enters birthday field in contact view
Reply With Quote
  #4 (permalink)  
Old 07-07-2008, 08:08 AM
Junior Member
 
Posts: 6
Default

Thanks for you info!

I came to the conclusion that since I first evaluated Open Xchange, then started to evaluate Zimbra, I will now give Horde Groupware a try. If I move back to zimbra I will vote.
__________________
ZCS 5.0.6 CE on Linux VServer with Ubuntu 8.04 Hardy Heron behind NAT and using a RelayHost

Last edited by Dorowan; 07-16-2008 at 02:19 AM..
Reply With Quote
  #5 (permalink)  
Old 07-16-2008, 12:47 AM
Moderator
 
Posts: 6,237
Default

That 100 vs 30 year difference might just have been us running different versions.

Prior to 5.0.7:
Quote:
Previously the limits were hard-coded. Max instances expanded were limited to 1200. There weren't separate limits for recurrence frequency, and all rules were limited to 30 years.
Change of behavior 5.0.7+: Bug 24926 - Configurable limits for recurrence expansion

zimbraCalendarRecurrenceMaxInstances 0
zimbraCalendarRecurrenceDailyMaxDays 730
zimbraCalendarRecurrenceWeeklyMaxWeeks 520
zimbraCalendarRecurrenceMonthlyMaxMonths 360
zimbraCalendarRecurrenceYearlyMaxYears 100
zimbraCalendarRecurrenceOtherFrequencyMaxYears 1

For no limitations, set limits to 0 (zero)

Server restart is required after adjusting limits. Appointments created with old limits will still have range based on the old limits. They will be updated to the new range upon any modification by the user. A migration script is needed to update all existing appointments if the user is not going to modify them manually.

These are set during a new install of ZCS and global config on upgrades.

When you upgrade to 5.0.7, to have users accounts set to these defaults settings, you will need to run zmfixcalendtime -a all.

When upgrading to 5.0.7 or later, to set recurring limits other than the defaults and update the existing appointments for all accounts with these limits:
1. Run zmprov mcf <attribute> <value>
2. zmmailboxdctl restart
3. Run zmfixcalendtime -a all to make the change to all accounts on the server.

Note: to change a single account, run zmfixcalendtime -a <user>

http://www.zimbra.com/forums/announc...html#post62754
Reply With Quote
  #6 (permalink)  
Old 07-16-2008, 02:20 AM
Junior Member
 
Posts: 6
Default

Thanks! I will try Kolab + Horde first an if I come back to zimbra I will use this tip.
__________________
ZCS 5.0.6 CE on Linux VServer with Ubuntu 8.04 Hardy Heron behind NAT and using a RelayHost
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Similar Threads

Why Join?

Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.

blog.zimbra.com




 

SEO by vBSEO ©2011, Crawlability, Inc.