Plone Zope Time Zone Confusion.

I am having a problem with the time that that Plone claims
that an object 
was edited, NOT matching the time

Zope, my server and my self know it to be. In my case its
off by 4 hours.



Plone version overview
Plone 2.5.2,
CMF-1.6.2,
Zope (Zope 2.9.6-final, python 2.4.3, win32),
Five 1.3.8,
Python 2.4.3 (#69, Mar 29 2006, 17:35:34) [MSC v.1310 32 bit
(Intel)],
PIL 1.1.5



I had suspected that this was being caused by this being ran
on a Windows 
Server, however I am also testing Plone on a Red Hat Linux
server and when I 
went back to it I noted that I am having the same problem
with Plone here as 
well. On both servers I have experimented by changing the
time zones via the 
OS and separately added TZ and the desired time zone in
runzope. It detects 
the time zone changes in the OS, but not via TZ. Unlike the
situation at 
http://www
.zettai.net/Forums/04/1061793085 I have "full"
control of the 
Linux server, and significant control over the Windows 2003
server.

I am using this code to display the time "<div 
tal:content="context/ZopeTime">" . It
returns this "2007/03/20 09:10:52.939 
GMT-4". Is this saying that my time is 9:10 and that it
is GMT-4 or is it 
saying that it thinks GMT is "9:10" and that my
actual time is (9:10 - 
4hours) = 5:10 my time?



When I edited a page at "2007/03/20 09:10:52.939
GMT-4" time  Plone reports 
"by Dan - last modified 2007-03-20 05:10"




_______________________________________________
Setup mailing list
Setuplists.plone.org
http://
lists.plone.org/mailman/listinfo/setup

I also had this issue. AFAIK, it is a Zope issue. I had to
workaround by
changing the timezone on my server to match what Zope
expected. GMT+0 ...

Might not be the same issue, but I did file a bug in the
Plone bugtracker.

Dan Campbell wrote:
> I am having a problem with the time that that Plone
claims that an object 
> was edited, NOT matching the time
>
> Zope, my server and my self know it to be. In my case
its off by 4 hours.
>
>
>
> Plone version overview
> Plone 2.5.2,
> CMF-1.6.2,
> Zope (Zope 2.9.6-final, python 2.4.3, win32),
> Five 1.3.8,
> Python 2.4.3 (#69, Mar 29 2006, 17:35:34) [MSC v.1310
32 bit (Intel)],
> PIL 1.1.5
>
>
>
> I had suspected that this was being caused by this
being ran on a Windows 
> Server, however I am also testing Plone on a Red Hat
Linux server and when I 
> went back to it I noted that I am having the same
problem with Plone here as 
> well. On both servers I have experimented by changing
the time zones via the 
> OS and separately added TZ and the desired time zone in
runzope. It detects 
> the time zone changes in the OS, but not via TZ. Unlike
the situation at 
> http://www
.zettai.net/Forums/04/1061793085 I have "full"
control of the 
> Linux server, and significant control over the Windows
2003 server.
>
> I am using this code to display the time "<div

> tal:content="context/ZopeTime">" . It
returns this "2007/03/20 09:10:52.939 
> GMT-4". Is this saying that my time is 9:10 and
that it is GMT-4 or is it 
> saying that it thinks GMT is "9:10" and that
my actual time is (9:10 - 
> 4hours) = 5:10 my time?
>
>
>
> When I edited a page at "2007/03/20 09:10:52.939
GMT-4" time  Plone reports 
> "by Dan - last modified 2007-03-20 05:10"
>
>
>
>
> _______________________________________________
> Setup mailing list
> Setuplists.plone.org
> http://
lists.plone.org/mailman/listinfo/setup
>   

_______________________________________________
Setup mailing list
Setuplists.plone.org
http://
lists.plone.org/mailman/listinfo/setup

Yes, setting the server's time zone to "GMT" does
cause the times to be 
presented "correctly", but this will cause other
problems because the data 
needs to be properly time stamped and time zoned for
government records.

I did see something about a time bug in Zope 2.9.6 and had
considered 
upgrading to 2.10.? However I think that Plone 2.5.2 does
not work with that 
version, so if true, that is not a solution.

"Jonathan Steffan" <jonfedoraunity.org> wrote
in 
message news:46000EB7.8040000fedoraunity.org...
>I also had this issue. AFAIK, it is a Zope issue. I had
to workaround by
> changing the timezone on my server to match what Zope
expected. GMT+0 ...
>
> Might not be the same issue, but I did file a bug in
the Plone bugtracker.
>
> Dan Campbell wrote:
>> I am having a problem with the time that that Plone
claims that an object
>> was edited, NOT matching the time
>>
>> Zope, my server and my self know it to be. In my
case its off by 4 hours.
>>
>>
>>
>> Plone version overview
>> Plone 2.5.2,
>> CMF-1.6.2,
>> Zope (Zope 2.9.6-final, python 2.4.3, win32),
>> Five 1.3.8,
>> Python 2.4.3 (#69, Mar 29 2006, 17:35:34) [MSC
v.1310 32 bit (Intel)],
>> PIL 1.1.5
>>
>>
>>
>> I had suspected that this was being caused by this
being ran on a Windows
>> Server, however I am also testing Plone on a Red
Hat Linux server and 
>> when I
>> went back to it I noted that I am having the same
problem with Plone here 
>> as
>> well. On both servers I have experimented by
changing the time zones via 
>> the
>> OS and separately added TZ and the desired time
zone in runzope. It 
>> detects
>> the time zone changes in the OS, but not via TZ.
Unlike the situation at
>> http://www
.zettai.net/Forums/04/1061793085 I have "full"
control of the
>> Linux server, and significant control over the
Windows 2003 server.
>>
>> I am using this code to display the time
"<div
>> tal:content="context/ZopeTime">"
. It returns this "2007/03/20 
>> 09:10:52.939
>> GMT-4". Is this saying that my time is 9:10
and that it is GMT-4 or is it
>> saying that it thinks GMT is "9:10" and
that my actual time is (9:10 -
>> 4hours) = 5:10 my time?
>>
>>
>>
>> When I edited a page at "2007/03/20
09:10:52.939 GMT-4" time  Plone 
>> reports
>> "by Dan - last modified 2007-03-20
05:10"
>>
>>
>>
>>
>> _______________________________________________
>> Setup mailing list
>> Setuplists.plone.org
>> http://
lists.plone.org/mailman/listinfo/setup
>>
> 




_______________________________________________
Setup mailing list
Setuplists.plone.org
http://
lists.plone.org/mailman/listinfo/setup

Hey,

> Yes, setting the server's time zone to "GMT"
does cause the times to be 
> presented "correctly", but this will cause
other problems because the data 
> needs to be properly time stamped and time zoned for
government records.
> 
> I did see something about a time bug in Zope 2.9.6 and
had considered 
> upgrading to 2.10.? However I think that Plone 2.5.2
does not work with that 
> version, so if true, that is not a solution.

known Zope issue: http://www.z
ope.org/Collectors/Zope/2191

BTW a quick search on Plone bug tracker point us to at
least:

http://dev.plo
ne.org/plone/ticket/5987
http://dev.plo
ne.org/plone/ticket/6052
http://dev.plo
ne.org/plone/ticket/6062
http://dev.plo
ne.org/plone/ticket/6237



-- 
 ___________________________________________________________
________

       Dorneles Treméa · Developer · Plone Solutions ·
Brazil

   Consulting · Training · Development · http://plonesolutions.com
 ___________________________________________________________
________

  Plone Foundation · http://plone.org/foundati
on · Protecting Plone


_______________________________________________
Setup mailing list
Setuplists.plone.org
http://
lists.plone.org/mailman/listinfo/setup

Okay, so if I understand this correctly Zope 2.9.6 is the
"cause" of this. 
Based on Zope's information it looks like I can do one of 2
things, for the 
short term, to correct the problem.

1. I could use Zope 2.9.5. If I understand correctly I you
would just 
install Zope 2.9.5 in its own directory and then copy over
my database from 
Zope 2.9.6?

2. I could apply a patch to Zope 2.9.6. I am a little
confused about how 
patches are applied to Zope and Plone. Elsewhere I see
information about 
placing patches in the appropriate "Products"
directory.

I am in the development and learning stage for Plone and
Zope and I am a 
little overwhelmed. Where can I find help for a total newb
Plone / Zope 
administrator? Particularly patching and upgrading.


"Dorneles Treméa" <deoplonesolutions.com> 
wrote in message news:etp9p9$9ps$1sea.gmane.org...
> Hey,
>
>> Yes, setting the server's time zone to
"GMT" does cause the times to be
>> presented "correctly", but this will
cause other problems because the 
>> data
>> needs to be properly time stamped and time zoned
for government records.
>>
>> I did see something about a time bug in Zope 2.9.6
and had considered
>> upgrading to 2.10.? However I think that Plone
2.5.2 does not work with 
>> that
>> version, so if true, that is not a solution.
>
> known Zope issue: http://www.z
ope.org/Collectors/Zope/2191
>
> BTW a quick search on Plone bug tracker point us to at
least:
>
> http://dev.plo
ne.org/plone/ticket/5987
> http://dev.plo
ne.org/plone/ticket/6052
> http://dev.plo
ne.org/plone/ticket/6062
> http://dev.plo
ne.org/plone/ticket/6237
>
> 
>
> -- 
>
____________________________________________________________
_______
>
>       Dorneles Treméa · Developer · Plone Solutions ·
Brazil
>
>   Consulting · Training · Development · http://plonesolutions.com
>
____________________________________________________________
_______
>
>  Plone Foundation · http://plone.org/foundati
on · Protecting Plone
>
> 




_______________________________________________
Setup mailing list
Setuplists.plone.org
http://
lists.plone.org/mailman/listinfo/setup

On Wed, 21 Mar 2007 13:45:58 -0700, Dorneles Treméa  
<deoplonesolutions.com> wrote:

>> Okay, so if I understand this correctly Zope 2.9.6
is the "cause" of  
>> this.
>> Based on Zope's information it looks like I can do
one of 2 things, for  
>> the
>> short term, to correct the problem.
>>
>> 1. I could use Zope 2.9.5. If I understand
correctly I you would just
>> install Zope 2.9.5 in its own directory and then
copy over my database  
>> from
>> Zope 2.9.6?
>>
>> 2. I could apply a patch to Zope 2.9.6. I am a
little confused about how
>> patches are applied to Zope and Plone. Elsewhere I
see information about
>> placing patches in the appropriate
"Products" directory.
>
> 3. You could replace your current DateTime.py file with
the last
> revision from:
>
> http://svn.zope.org/Zope/branches/2.9/lib/p
ython/DateTime/DateTime.py

...or

4. Wait for the next release of Zope that should be out
shortly to address  
the XSS security issue that was just hotfixed. ;)

But #3 is probably what will get you up and running today.

-- 
Alexander Limi · http://limi.net


_______________________________________________
Setup mailing list
Setuplists.plone.org
http://
lists.plone.org/mailman/listinfo/setup

Thanks guys, I have already tried option 2 with the patch
command and got 
...

dandeadhat DateTime]$ patch < DateTime-ISO8601.patch

can't find file to patch at input line 5

Perhaps you should have used the -p or --strip option?

The text leading up to this was:

--------------------------

|Index: tests/testDateTime.py

|===========================================================
========

|--- tests/testDateTime.py      (revisão 71022)

|+++ tests/testDateTime.py      (cópia de trabalho)

--------------------------

File to patch:

Skip this patch? [y] y

Skipping patch.

18 out of 18 hunks ignored

patching file DateTime.py

Reversed (or previously applied) patch detected!  Assume -R?
[n] y

Hunk #7 succeeded at 518 with fuzz 1 (offset 4 lines).

Hunk #8 FAILED at 559.

Hunk #9 succeeded at 565 (offset -1 lines).

Hunk #10 FAILED at 600.

Hunk #11 succeeded at 636 (offset 4 lines).

Hunk #12 succeeded at 643 (offset -1 lines).

Hunk #13 succeeded at 738 (offset 7 lines).

Hunk #14 succeeded at 1630 with fuzz 2 (offset 32 lines).

Hunk #15 FAILED at 1771.

3 out of 15 hunks FAILED -- saving rejects to file
DateTime.py.rej



"Alexander Limi" <limiplone.org> wrote in 
message news:op.tpj5bpy3vhba00-emo...
> On Wed, 21 Mar 2007 13:45:58 -0700, Dorneles Treméa 
> <deoplonesolutions.com> wrote:
>
>>> Okay, so if I understand this correctly Zope
2.9.6 is the "cause" of 
>>> this.
>>> Based on Zope's information it looks like I can
do one of 2 things, for 
>>> the
>>> short term, to correct the problem.
>>>
>>> 1. I could use Zope 2.9.5. If I understand
correctly I you would just
>>> install Zope 2.9.5 in its own directory and
then copy over my database 
>>> from
>>> Zope 2.9.6?
>>>
>>> 2. I could apply a patch to Zope 2.9.6. I am a
little confused about how
>>> patches are applied to Zope and Plone.
Elsewhere I see information about
>>> placing patches in the appropriate
"Products" directory.
>>
>> 3. You could replace your current DateTime.py file
with the last
>> revision from:
>>
>> http://svn.zope.org/Zope/branches/2.9/lib/p
ython/DateTime/DateTime.py
>
> ...or
>
> 4. Wait for the next release of Zope that should be out
shortly to address 
> the XSS security issue that was just hotfixed. ;)
>
> But #3 is probably what will get you up and running
today.
>
> -- 
> Alexander Limi · http://limi.net
>
> 




_______________________________________________
Setup mailing list
Setuplists.plone.org
http://
lists.plone.org/mailman/listinfo/setup

I just tried option 3 and it worked great! The times are
displaying 
correctly now! Jonathan, give it a try. It should work just
as easily for 
you.

Now I am one step closer to removing my Plone / Zope
training wheels.

"Alexander Limi" <limiplone.org> wrote in 
message news:op.tpj5bpy3vhba00-emo...
> On Wed, 21 Mar 2007 13:45:58 -0700, Dorneles Treméa 
> <deoplonesolutions.com> wrote:
>
>>> Okay, so if I understand this correctly Zope
2.9.6 is the "cause" of 
>>> this.
>>> Based on Zope's information it looks like I can
do one of 2 things, for 
>>> the
>>> short term, to correct the problem.
>>>
>>> 1. I could use Zope 2.9.5. If I understand
correctly I you would just
>>> install Zope 2.9.5 in its own directory and
then copy over my database 
>>> from
>>> Zope 2.9.6?
>>>
>>> 2. I could apply a patch to Zope 2.9.6. I am a
little confused about how
>>> patches are applied to Zope and Plone.
Elsewhere I see information about
>>> placing patches in the appropriate
"Products" directory.
>>
>> 3. You could replace your current DateTime.py file
with the last
>> revision from:
>>
>> http://svn.zope.org/Zope/branches/2.9/lib/p
ython/DateTime/DateTime.py
>
> ...or
>
> 4. Wait for the next release of Zope that should be out
shortly to address 
> the XSS security issue that was just hotfixed. ;)
>
> But #3 is probably what will get you up and running
today.
>
> -- 
> Alexander Limi · http://limi.net
>
> 




_______________________________________________
Setup mailing list
Setuplists.plone.org
http://
lists.plone.org/mailman/listinfo/setup