Closed (won't fix)
Project:
Event
Version:
5.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
7 Mar 2008 at 15:25 UTC
Updated:
25 Mar 2010 at 19:56 UTC
This problem is persistent in 5.x-1.0 as well.
Adding an event using the node/add/event form only results in a database entry where:
Have tried running update.php, checked the SQL (5.0.51a) database for errors, running cron, disabling modules, restarting apache. Nothing have given me any clue as to why the correct date and time is not saved to the database table. A fresh copy from drupal.org does not solve the problem either.
Modules which have been installed which I guess might have something to do with this:
However, disabling all or combinations of these have no effect on the problem.
Comments
Comment #1
devkinetic commentedthis screencast has a great run-through of managing timezones between drupal/your server/php/mysql. It goes thtough lots of the settings that can make this go flukey. Also, its a great start off for using calender and cck to replace event ( should you be moving to 6/7 )
http://www.doitwithdrupal.com/2009/sessions/dates-calendars-drupal
Comment #2
killes@www.drop.org commentedPlease migrate to event 5.2-dev if you have problems with timestamps.
Comment #3
NiklasBr commentedCustomer and Drupal providers/developers gave up trying to fix this some time ago. For all I care may keep current status on this issue.