Recurring appointments

[sean_cunneen]

Hi, I have been using the hosted demo to investigate the Zimbra functionality. An important feature for me is the ability to edit an instance of a recurring appointment. When ever I try this in the demo it errors. I couldn't see any reference to this problem in the bug list - so I'm not sure if this is known limitation, or an issue with the demo host.
I have replicated this issue when adjusting pretty much any single field of the appointment. I am connecting from a Mac (10.4.9) and have tried with FF 2.0.0.3 and Safari 2.0.4.

Thanks

Sean

PS I did click the "send error" button if that goes anywhere useful.

[phoenix]

Welcome to the forums.

You can certainly edit an instance of a recurring appointment and change some of the details then save it, that only changes the one instance. Is that what you're trying to do?

[edit]FWIW, I've just tried the hosted demo and changed an item in the recurring appointment and saved it without problems.

[KevinH]

The hosted demo is running an older release so it may have been fixed in the most recent.

[sean_cunneen]

I don't know what is wrong with my setup. I created a new appointment recurring daily for 5 days. I can successfully edit the series to change the time. However I attempted to edit the first appointment to add some text. When saving the usual error occurs. The details are:

msg - invalid request: invalid time zone "(GMT+09.00) Auto-Detected"
com.zimbra.common.service.ServiceException: invalid request: invalid time zone "(GMT+09.00) Auto-Detected"
at com.zimbra.common.service.ServiceException.INVALID _REQUEST(ServiceException.java:182)
at com.zimbra.cs.service.mail.CalendarUtils.lookupAnd AddToTzList(CalendarUtils.java:323)
at com.zimbra.cs.service.mail.CalendarUtils.parseDate Time(CalendarUtils.java:288)
at com.zimbra.cs.service.mail.CalendarUtils.parseDate Time(CalendarUtils.java:279)
at com.zimbra.cs.service.mail.CalendarUtils.parseInvi teElementCommon(CalendarUtils.java:655)
at com.zimbra.cs.service.mail.CalendarUtils.parseInvi teForCreate(CalendarUtils.java:120)
at com.zimbra.cs.service.mail.CreateCalendarItemExcep tion$CreateCalendarItemExceptionInviteParser.parse InviteElement(CreateCalendarItemException.java:66)
at com.zimbra.cs.service.mail.ParseMimeMessage$Invite Parser.parse(ParseMimeMessage.java:139)
at com.zimbra.cs.service.mail.ParseMimeMessage.parseM imeMsgSoap(ParseMimeMessage.java:254)
at com.zimbra.cs.service.mail.CalendarRequest.handleM sgElement(CalendarRequest.java:109)
at com.zimbra.cs.service.mail.CreateCalendarItemExcep tion.handle(CreateCalendarItemException.java:115)
at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:262)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:162)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:84)
at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:223)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:709)
at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:162)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:802)
at org.apache.catalina.core.ApplicationFilterChain.in ternalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.do Filter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invo ke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invo ke(StandardContextValve.java:178)
at org.apache.catalina.core.StandardHostValve.invoke( StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke (ErrorReportValve.java:105)
at org.apache.catalina.core.StandardEngineValve.invok e(StandardEngineValve.java:107)
at org.apache.catalina.valves.AccessLogValve.invoke(A ccessLogValve.java:541)
at org.apache.catalina.connector.CoyoteAdapter.servic e(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(H ttp11Processor.java:869)
at org.apache.coyote.http11.Http11BaseProtocol$Http11 ConnectionHandler.processConnection(Http11BaseProt ocol.java:667)
at org.apache.tomcat.util.net.PoolTcpEndpoint.process Socket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThr ead.runIt(LeaderFollowerWorkerThread.java:80)
at org.apache.tomcat.util.threads.ThreadPool$ControlR unnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:595)

code - service.INVALID_REQUEST
method - ZmCsfeCommand.prototype.invoke
detail - soap:Sender