RE: Civicspace 0.8.0.1, based on Drupal.

When adding stories or blog entries, I noticed my default setting was UTC +6:00, not -6:00. Basically, Alabama (Chicago time in Windows :) is set to Central Time. Central time changes from -6:00 to -5:00, based on the season (AKA: Daylight Savings Time - another topic). I mistakenly set my Drupal site time, through the "Settings", to UTC +6:00. I shortly thereafter found it and changed it to UTC -6:00 as it should be. But, when I post new stories or blog entries, it just slapped on +6:00 unless I manually corrected it. This was very frustrating.

I found the [user] error that caused all my posts to be marked +6:00. It was a user setting, that obviously was set that way when I had the site's default time set to +6:00, which flowed through to my personal setting. I changed it in my personal settings, and it was no longer a problem

Bug? Well, I think so. There should be an "automated site time" option, where my time as a user is the same as the site's. There are many reasons a site's time may change and I might want to stay in sync as a user (especially a content contributor). For example, we live in one of those Daylight Savings or Standard Time zones which changes twice a year. For half the year we are -6:00, and the other chunk we are -5:00.

I wish the world were on UTC! But, since we aren't, those settings should flow unless specifically modified by the user for their account. And, contributed content should display by the site's time, not the user's. If someone in England posted data in a +0:00 zone, that doesn't change what time is on the site. So, showing them five hours off the time we have on the site, makes their content look like it's posted in the future. That's wrong. Now, it would be fine to note that the person who posted the content was in a different time zone, but that's another issue and should be a separate field when displayed.

Note: There should be a question and answer setup section for new accounts, so users are led to make those settings. But, that's another issue we'll handle on a different day.