Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 94312 - Plone callendar is wrong on zope installations
Summary: Plone callendar is wrong on zope installations
Status: RESOLVED UPSTREAM
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Server (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: net-zope (OBSOLETE)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-05-28 13:26 UTC by Pupeno
Modified: 2005-08-28 05:58 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Pupeno 2005-05-28 13:26:45 UTC
This is the general description of the problem: 
 
I had a set of Plone sites working on some computer and I moved the Data.fs to 
another server (phisically) and since I've done that, the calendars are acting 
all strange. 
The show last month instead of current (now is May, they show April), with last 
month's layout (that is, April's layout) but the actual events are the one of 
May (so, if someone is going to happen on May 27th (Friday), it looks like it 
was going to happen on Apr 27th (Wednesday). 
Also events are shifted by one hour when I edit them. That is, I create an 
event starting at 21:00hs, save it and everything is all-right, but when I edit 
it, 20:00hs is put in the form and if I save it, it stays on 20:00hs. And this 
ocurs all the times, if I edit and save it 20 times, I'll reach 00:00hs. 
This happens to every Plone site that I have running on that zope instance, for 
you to see: http://pupeno.com (there's an event on June, it's shown on May), 
http://fsreaders.com.ar (there's an event on May, showing on Apr), 
http://sandrafernandez.com.ar, http://osteopatiaargentina.com.ar, 
http://viejabotica.com.ar and http://kalmarstokoe.com.ar) 
Note: there was a slight problem in the migration, maybe it is related, but I'm 
not sure. The computer that were running this instances was running Plone 2.0.5 
and when I started using this new one, it was running Plone 2.0.4, I latter 
switched to 2.0.5 but that didn't solve it. 
Any help is appretiated, I'll provide any information that is needed to debug 
this problem. 
 
Now, it seems the problem is Gentoo associated because other people reported 
the same problem on Gentoo, here it is the bug reported for the Plone 
developers (and the place to send feedback to Plone developers): 
http://plone.org/collector/4095 

Reproducible: Always
Steps to Reproduce:
1.
2.
3.
Comment 1 Radoslaw Stachowiak (RETIRED) gentoo-dev 2005-08-28 05:58:37 UTC
This is not gentoo related, please reopen if you have more information.