Closed (outdated)
Project:
Advertisement
Version:
6.x-2.2
Component:
ad module
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
25 Aug 2011 at 20:36 UTC
Updated:
19 Sep 2024 at 11:29 UTC
Jump to comment: Most recent
Comments
Comment #1
robobeau commentedWell, I figured out what my problem was. All the "format_date" functions lack the timezone argument, so it assume's the user's timezone (America/NewYork, in my case). If I enter 12:00, it'll save correctly into the DB, but when I re-edit it, the default value goes through "format_date", converts to GMT -4, and spits out 8:00.
Problem is, I don't want/need a timezone conversion, so I modified all the "format_date" functions to have a 0 as the timezone argument.
Can anyone shed some light as to why the conversion is taking place in the first place? Is this intended behavior? And wouldn't it better if timezone conversion was optional?
Comment #2
mèche commentedI have the same bug but give 0 as the timezone argument didn't fix it...
Comment #3
lrwebks commentedDrupal 6 is EOL and no longer supported. Closing this as outdated for that reason. Thanks for your contribution!