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

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 03-10-2011, 08:03 AM
Junior Member
 
Posts: 7
Default ZCS 7.0.1 Web Client Print Issue

Hi,

We upgraded from:

zcs-NETWORK-7.0.0_GA_3105.UBUNTU10_64.20110304195508.tgz

To

zcs-NETWORK-7.0.1_GA_3105.UBUNTU10_64.20110304195508.tgz

The issue is that when a user using the Web Client selects Calendar, View and selects Day, when they click the print icon, it comes up with wanting to print the Start Of The Week day. So if a user selects to print Thursday, when the print preview page comes up, it shows Monday.

If I change the Start of the Week day to be Tuesday, the print preview page comes up as being Tuesday, no matter what other day of that week I select.

I have opened up a ticket as this being a bug under ticket 57769 in the Bugzilla.

Anyone else having this issue in ZCS 7.0.1 x64 using Ubuntu 10.04 or any other OS/hardware builds?

Thanks and regards,

Tim
Reply With Quote
  #2 (permalink)  
Old 03-10-2011, 10:42 PM
New Member
 
Posts: 3
Default

I'm glad I saw this! I just upgraded about an hour ago and I have the same issue. We have some drivers that print out the day view every morning before they leave, this will be a problem for them.
Thanks for the heads up.


I just tried printing a day view from the Desktop 7 client and got this error:

HTTP ERROR 500

Problem accessing /zimbra/h/printcalendar. Reason:

Problems calling function 'zm:lightenColor'

Caused by:

javax.el.ELException: Problems calling function 'zm:lightenColor'
at com.sun.el.parser.AstFunction.getValue(AstFunction .java:132)
at com.sun.el.ValueExpressionImpl.getValue(ValueExpre ssionImpl.java:206)
at org.apache.jasper.runtime.PageContextImpl.evaluate Expression(PageContextImpl.java:1001)
at org.apache.jsp.h.printcalendar._jspx_meth_c_forEac h_0(Unknown Source)
at org.apache.jsp.h.printcalendar._jspService(Unknown Source)
at org.apache.jasper.runtime.HttpJspBase.service(Http JspBase.java:109)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:820)
at org.apache.jasper.servlet.JspServletWrapper.servic e(JspServletWrapper.java:389)
at org.apache.jasper.servlet.JspServlet.serviceJspFil e(JspServlet.java:486)
at org.apache.jasper.servlet.JspServlet.service(JspSe rvlet.java:380)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:820)
at com.zimbra.webClient.servlet.JspServlet.service(Js pServlet.java:64)
at org.mortbay.jetty.servlet.ServletHolder.handle(Ser vletHolder.java:511)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1166)
at com.zimbra.cs.servlet.SetHeaderFilter.doFilter(Set HeaderFilter.java:79)
at com.zimbra.webClient.filters.SetHeaderFilter.doFil ter(SetHeaderFilter.java:241)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1157)
at org.mortbay.jetty.servlet.ServletHandler.handle(Se rvletHandler.java:388)
at org.mortbay.jetty.security.SecurityHandler.handle( SecurityHandler.java:218)
at org.mortbay.jetty.servlet.SessionHandler.handle(Se ssionHandler.java:182)
at org.mortbay.jetty.handler.ContextHandler.handle(Co ntextHandler.java:765)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebA ppContext.java:422)
at org.mortbay.jetty.handler.ContextHandlerCollection .handle(ContextHandlerCollection.java:230)
at org.mortbay.jetty.handler.HandlerCollection.handle (HandlerCollection.java:114)
at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:152)
at org.mortbay.jetty.handler.rewrite.RewriteHandler.h andle(RewriteHandler.java:230)
at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:326)
at org.mortbay.jetty.HttpConnection.handleRequest(Htt pConnection.java:543)
at org.mortbay.jetty.HttpConnection$RequestHandler.he aderComplete(HttpConnection.java:929)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser. java:549)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpPa rser.java:212)
at org.mortbay.jetty.HttpConnection.handle(HttpConnec tion.java:405)
at org.mortbay.io.nio.SelectChannelEndPoint.run(Selec tChannelEndPoint.java:410)
at org.mortbay.thread.BoundedThreadPool$PoolThread.ru n(BoundedThreadPool.java:451)
Caused by: java.lang.NumberFormatException: For input string: ""
at java.lang.NumberFormatException.forInputString(Unk nown Source)
at java.lang.Integer.parseInt(Unknown Source)
at java.lang.Integer.valueOf(Unknown Source)
at java.lang.Integer.decode(Unknown Source)
at java.awt.Color.decode(Unknown Source)
at com.zimbra.cs.taglib.bean.BeanUtils.lightenColor(B eanUtils.java:1416)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknow n Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Un known Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.sun.el.parser.AstFunction.getValue(AstFunction .java:127)
... 34 more

Caused by:

java.lang.NumberFormatException: For input string: ""
at java.lang.NumberFormatException.forInputString(Unk nown Source)
at java.lang.Integer.parseInt(Unknown Source)
at java.lang.Integer.valueOf(Unknown Source)
at java.lang.Integer.decode(Unknown Source)
at java.awt.Color.decode(Unknown Source)
at com.zimbra.cs.taglib.bean.BeanUtils.lightenColor(B eanUtils.java:1416)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknow n Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Un known Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.sun.el.parser.AstFunction.getValue(AstFunction .java:127)
at com.sun.el.ValueExpressionImpl.getValue(ValueExpre ssionImpl.java:206)
at org.apache.jasper.runtime.PageContextImpl.evaluate Expression(PageContextImpl.java:1001)
at org.apache.jsp.h.printcalendar._jspx_meth_c_forEac h_0(Unknown Source)
at org.apache.jsp.h.printcalendar._jspService(Unknown Source)
at org.apache.jasper.runtime.HttpJspBase.service(Http JspBase.java:109)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:820)
at org.apache.jasper.servlet.JspServletWrapper.servic e(JspServletWrapper.java:389)
at org.apache.jasper.servlet.JspServlet.serviceJspFil e(JspServlet.java:486)
at org.apache.jasper.servlet.JspServlet.service(JspSe rvlet.java:380)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:820)
at com.zimbra.webClient.servlet.JspServlet.service(Js pServlet.java:64)
at org.mortbay.jetty.servlet.ServletHolder.handle(Ser vletHolder.java:511)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1166)
at com.zimbra.cs.servlet.SetHeaderFilter.doFilter(Set HeaderFilter.java:79)
at com.zimbra.webClient.filters.SetHeaderFilter.doFil ter(SetHeaderFilter.java:241)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1157)
at org.mortbay.jetty.servlet.ServletHandler.handle(Se rvletHandler.java:388)
at org.mortbay.jetty.security.SecurityHandler.handle( SecurityHandler.java:218)
at org.mortbay.jetty.servlet.SessionHandler.handle(Se ssionHandler.java:182)
at org.mortbay.jetty.handler.ContextHandler.handle(Co ntextHandler.java:765)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebA ppContext.java:422)
at org.mortbay.jetty.handler.ContextHandlerCollection .handle(ContextHandlerCollection.java:230)
at org.mortbay.jetty.handler.HandlerCollection.handle (HandlerCollection.java:114)
at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:152)
at org.mortbay.jetty.handler.rewrite.RewriteHandler.h andle(RewriteHandler.java:230)
at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:326)
at org.mortbay.jetty.HttpConnection.handleRequest(Htt pConnection.java:543)
at org.mortbay.jetty.HttpConnection$RequestHandler.he aderComplete(HttpConnection.java:929)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser. java:549)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpPa rser.java:212)
at org.mortbay.jetty.HttpConnection.handle(HttpConnec tion.java:405)
at org.mortbay.io.nio.SelectChannelEndPoint.run(Selec tChannelEndPoint.java:410)
at org.mortbay.thread.BoundedThreadPool$PoolThread.ru n(BoundedThreadPool.java:451)

Powered by Jetty://




Quote:
Originally Posted by Yopofun View Post
Hi,

We upgraded from:

zcs-NETWORK-7.0.0_GA_3105.UBUNTU10_64.20110304195508.tgz

To

zcs-NETWORK-7.0.1_GA_3105.UBUNTU10_64.20110304195508.tgz

The issue is that when a user using the Web Client selects Calendar, View and selects Day, when they click the print icon, it comes up with wanting to print the Start Of The Week day. So if a user selects to print Thursday, when the print preview page comes up, it shows Monday.

If I change the Start of the Week day to be Tuesday, the print preview page comes up as being Tuesday, no matter what other day of that week I select.

I have opened up a ticket as this being a bug under ticket 57769 in the Bugzilla.

Anyone else having this issue in ZCS 7.0.1 x64 using Ubuntu 10.04 or any other OS/hardware builds?

Thanks and regards,

Tim

Last edited by GaryHarmon; 03-10-2011 at 11:05 PM.. Reason: More information
Reply With Quote
  #3 (permalink)  
Old 03-11-2011, 03:23 AM
Elite Member
 
Posts: 469
Default

Same issue 7.0.1 - CentOS 5.5_x64 - voting for your bug.
Reply With Quote
  #4 (permalink)  
Old 03-14-2011, 10:59 AM
Active Member
 
Posts: 45
Default

We are also experiencing a similar issue with printing emails that contain attachments.

I have filed bug# 57907
Reply With Quote
  #5 (permalink)  
Old 03-28-2011, 03:43 PM
New Member
 
Posts: 4
Default

Exact same issue here 7.0.1 on RHEL5 x64
Reply With Quote
  #6 (permalink)  
Old 03-29-2011, 02:19 AM
Junior Member
 
Posts: 7
Default

is there some kind of (temporary) fix.
I now have many people breathing down my neck and I do not want to downgrade the existing infrastructure.
Apparently its fixed in 7.1, anybody knows when this will be available?

cheers
lil
Reply With Quote
  #7 (permalink)  
Old 03-29-2011, 02:21 AM
Junior Member
 
Posts: 7
Default

I also tried to replace the jitty directory from 7.0 but that didn't seem to fix the issue.
Reply With Quote
  #8 (permalink)  
Old 03-29-2011, 02:39 AM
Special Member
 
Posts: 100
Default

It's a shame no one from zimbra give a hotfix for this
Reply With Quote
  #9 (permalink)  
Old 03-29-2011, 02:42 AM
Zimbra Consultant & Moderator
 
Posts: 20,313
Default

Quote:
Originally Posted by miguel View Post
It's a shame no one from zimbra give a hotfix for this
Hotfixes are generally not supplied for bugs except in very special circumstances. You should also go to the bug report and check it's current status then look in the Product Portal for any target release for the fix.
__________________
Regards


Bill
Reply With Quote
  #10 (permalink)  
Old 03-29-2011, 03:03 AM
Special Member
 
Posts: 100
Default

I think this is a very special circumstance for everyone who uses the web client as mail client, it's a basic function for who use calendaring which is never suppose to broke within an upgrade IMO
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.