Thread

OK, I really, really don’t want to, but I think I’ll need to login to see what’s happening if you don’t mind.  If you have no objections, could you create an admin account and PM me login info with a link to this thread please?

Sheesh.  Sorry Andy, I’ve been in there poking and I don’t see it.  I need to do some more tests on my end.  Is using the server offset a viable solution for you for now until I can dig into this further?

This is currently the only display by day i’m using on any of the installs I have on this server. So…For now I’m going to keep all the posts for a day before 6pm. If someone can’t get their post in by 6pm….i’ll have them future date it for the next morning. Temporary solution that doesn’t jack up everything.

Keep me posted. I’ll move on to my next project in the mean time.

thanks!

Hey Andy.  For now our solution will be to use the large offset, but could I ask you to make a feature request for a “display_by_localized_day” parameter?

For now I changed the parameter to display_by=“week” it shows way more posts than I like, but for the time being its better than the large offset. The large offset just totally jacks up my time. I can’t have someone write a post and go to set the time of the post and see that it is hours off. The week ending six hours earlier is easier to swallow than each day.

I will make that feature request.

I went and looked at the date in the weblog_titles table and sure enough it’s writing the timestamp date data six hours ahead. If EE is writing that field to be faster with display by day why doesn’t it write the time localized to the user already and include the time in the timestamp instead of just the date?

thanks…that’s my last questions and i’ll make my feature request and shut up.

Every user has different localized times, do the localized offset is calculated when the data comes out of the system (not when it goes in).  Unfortunately, it doesn’t currently add the offset to the day - so we need to build a feature here.