First of all, I have my Timezone configured as -0400 hours (Atlanta, GA)

When I input a time in a date/time field created by flexinode, the time that it displays is 4 hours behind. For instance, I will input a time of 5:30pm, and the time that is shown on the resulting page will be 1:30pm.

I am not sure how drupal works internally, but I would guess that the database always stores GMT times, and converts appropriately before and after storing. It seems that flexinode thinks that I am giving it GMT times, when I am actually giving it local times. At display time, it then converts the GMT time to what it thinks is my local time, thus displaying times that are 4 hours behind what I entered.

My workaround for this problem has been to change all date/time fields to text fields. This has been quite limiting.

- Rick

Comments

Nwallins’s picture

Nwallins commented

More info:
using Drupal 4.6.2 downloaded from drupal.org
CVS id for flexinode module: $Id: INSTALL,v 1.5 2004/08/01 02:36:31 JonBob Exp $
please email me if you need more info about my setup

anner’s picture

anner commented

I'm using drupal v 4.6.6 and fiexinode $Id: flexinode.module,v 1.46.2.7 2006/03/10 22:59:42 seanr Exp $

I'm having this same problem and I think it must be related to date/time storage. It happens like this:
-I enter 12:00 as my time
-when I submit the page, it displays that time at 08:00
-when I open that page for editing, it fills in the time as 08:00
-when I submit the page that time, it displays that time as 04:00

anner’s picture

anner commented

I've noticed the behavior goes away if you choose to enable configurable time zones, but then all the dates are always in GMT.