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:

  1. nid: works as expected
  2. event_start: always returns 0000-00-00 00:00:00
  3. event_end: always returns 0000-00-00 00:00:00
  4. timezone: works as expected
  5. start_in_dst: not sure, probably works as expected
  6. end_in_dst: not sure, probably works as expected
  7. has_time: works as expected
  8. has_end_date: works as expected

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.

More information

  • Drupal version 5.7 running on Apache 2 (OS X 10.5.2)
  • PHP version 5.2.4
  • Configurable time zones is enabled in the Date/time module

Modules which have been installed which I guess might have something to do with this:

  • CCK Date
  • Date API
  • Calendar

However, disabling all or combinations of these have no effect on the problem.

Comments

devkinetic’s picture

Component: Basic Event » Code

this 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

killes@www.drop.org’s picture

Status: Active » Closed (won't fix)

Please migrate to event 5.2-dev if you have problems with timestamps.

NiklasBr’s picture

Customer and Drupal providers/developers gave up trying to fix this some time ago. For all I care may keep current status on this issue.