Closed GoogleCodeExporter closed 9 years ago
Thanks Bill. I'm looking this. Can you attach the contents of
DNW_GetRecentPosts here? There should be a condition in that stored proc that
looks like:
AND DateSyndicated <= @CurrentDateTime
Which is the same clause used by the non-aggregate homepage
Original comment by haac...@gmail.com
on 21 May 2011 at 9:54
Also, can you attach a screenshot of the "Location Settings" section of the
admin/Configure.aspx page in your admin section?
Original comment by haac...@gmail.com
on 21 May 2011 at 9:57
Please see the attached document. I did find
AND DateSyndicated <= @CurrentDateTime
in numerous places in the code. The challenge is that for an individual blog
it sets @CurrentDateTime correctly based on the time zone of the blog. But on
the aggregated home page it just used the system time to compare to all entries
across blogs in different time zones.
I don't know if it's better to store everything in UTC (my suggestion) or have
BOTH the aggregated home page AND the aggregated RSS adjust for time zones.
Original comment by billgraz...@gmail.com
on 22 May 2011 at 1:27
Attachments:
Look at http://code.google.com/p/subtext/issues/detail?id=291 for more details.
Original comment by haac...@gmail.com
on 22 May 2011 at 10:01
Issue 291 has been merged into this issue.
Original comment by haac...@gmail.com
on 22 May 2011 at 10:01
@Bill, I worry about storing everything in UTC at this point because we'd have
to convert all existing data to UTC. I believe we store it using *your*
timezone (not the system's). So if the aggregate page is using the System
timezone, then I need to find that code and correct it.
Original comment by haac...@gmail.com
on 22 May 2011 at 10:11
Ok, I figured out the problem and it's a tricky one. When we get the blog posts
to display, we pass in the date and time according to *the blog* (as in the one
you configured). We then grab all posts that were published on or before that
date.
But in the case of the Aggregate blog, there is no configured date time. So it
defaults to the server's timezone. What this means is I can't pass in a single
date to the query. I'd have to pass in one per blog.
So it looks like storing everything in UTC would help us solve this problem,
but doing so creates its own big problem, which is converting all the existing
data to UTC. :(
But I think this is the right change, but it's quite a bit of work.
Original comment by haac...@gmail.com
on 22 May 2011 at 10:27
Fixed in r4213
Original comment by haac...@gmail.com
on 2 Jun 2011 at 3:36
Original issue reported on code.google.com by
billgraz...@gmail.com
on 21 May 2011 at 3:10