search

bishop335 / subtext

Automatically exported from code.google.com/p/subtext
0 stars 0 forks source link

WLW is putting the user time in the DateSyndicated column #258

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Write a post with WLW at least one time zone east of the server
2. Check the DateSyndicated column.  It will show the time in the time zone of 
the user instead of the time zone of the server.
3. DNW_GetRecentPosts compares DateSyndicated to a date parameter which I'm 
guessing is usually the server date.
4. Thus if the person is five hours ahead of the server their post won't show 
up on the aggregated home page for five hours.

What is the expected output? What do you see instead?
I expected the post to show up on the aggregated home page after being posted.

What version of the product are you using? On what operating system?
2.5.1.0

Please provide any additional information below.
This is an interesting little bug.  I'm not sure whether it makes sense to 
store everything in GMT or what.  It may be possible to override some of this 
with WLW -- haven't checked yet.

Original issue reported on code.google.com by billgraz...@gmail.com on 24 Aug 2010 at 2:24

GoogleCodeExporter commented 9 years ago 
I have this setting: my computer zone is CET and my server zone is Pacific 
time. And it always worked for me.

The DateSyndicated column is stored with the time converted to the timezone 
specified in the options/configure page in the "Location Settings".
Check that your time zone settings are correct.

Original comment by simone.chiaretta on 24 Aug 2010 at 2:34

GoogleCodeExporter commented 9 years ago 
I could not reproduce the problem. Make sure you go to Admin Options page: 
/admin/Configure.aspx

And take note of the "Location Settings" box. The field that says "Your 
timezone" should be the timezone where *you* are, not your server. If it's not, 
change it. Subtext knows the timezone of the server that's hosting it, but it 
doesn't necessarily know *your* timezone, which is why you have to tell it.

Once you do that, it should work fine for you.

Original comment by haac...@gmail.com on 16 May 2011 at 3:14

GoogleCodeExporter commented 9 years ago 
Sorry guys I didn't describe the problem well enough.  It works fine on my 
individual blog page.  The part that breaks is on the aggregated home page. The 
aggregated home page doesn't display the post at the same time that my 
individual blog does.

I started another issue with a better description: 
http://code.google.com/p/subtext/issues/detail?id=300

Original comment by billgraz...@gmail.com on 21 May 2011 at 3:15