With that change made it has put the times in my control panel back into reason, but the issue with it displaying only the latest entry after 6pm by itself still exists.
Could you try editing an entry and resettitng its time to 4pm, and then back to 6pm for me?
If that doesn’t work, just to be sure I’ve got eveything straight, could you in a single sentence explain to me what you want to happen? Also, can you share the minimal template that shows us your problem? The fact that its working (presumably same code, localization settings etc) only highlights the inconsistencies across various servers. This is a very problematic area for us because of all the different possibilities.
I guess Derek what I’m trying to wrap my head around it that EE uses one date to determine if an entry should be displayed. Then it uses another to output the date shown on the screen. Is that right?
display_by is kind of an exception to the rule. In general, EE will use the same date information to determine both whether an entry is appropriate for display and (if it is) what date to show. In order to group by day, month or year in a way that is performance friendly, we also store those pieces of info discretely. You can see all these in your weblog_titles table if you’re interested (entry_date, day, month, year). Entry date is fist localized, and then day, month and year information is extracted from there. So they should all be the same. Because of this, in order to get this working “correctly” we’ll need to get the localization working. It just might be ultra tricky.
Your issue is clearly that your server is somehow off by 6 hours, so after 6pm it thinks an entry is the following day. We should be able to fix this up for you.
What is totally puzzling is that the server is set to central time. I’m in central time. All the users are set to central time. The only thing that I gather is not is the database stores all dates in GMT. Isn’t that normal?
Correct. The date information of the database should be irrelevent here, correct. It’ll only matter what time the server is at, and the users localization information at that moment.