Hi, super-useful module. But I have users in different timezones. When they create a new node that has a date component using the system default node/add/content_typeX method, the current date is set with their timezone (via Locale settings) taken in to account.

However, when they use the form-block equivalent (which is way cooler and faster and awesomer) the block form shows the server's default timezone.

So, my server is in Los Angeles. If a user who has their time zone set to Toronto (3 hours time difference) creates a node the 'standard' way, it shows Toronto time as the default in the date field. But if the same user uses the block-form method to create the same node-type, it shows the Los Angeles time as the default.

My apologies if this is not a bug but instead a setting that I missed. I tried searching on both Drupal.org and Google with no luck.

If you need more info, or a working example, let me know.

Cheers,
Dean

Comments

mikey_p’s picture

Issue summary: View changes
Issue tags: +7.x-1.0 release blocker
mikey_p’s picture

I'll look into this, but it's surprising that this is happening as this module doesn't do any modifications of time or timezones at all.

joseph.olstad’s picture

I suggest trying an updated version of the date module https://drupal.org/project/date
this should fix the issue.

joseph.olstad’s picture

Status: Active » Postponed (maintainer needs more info)