values unix_event_start and unix_event_end not updated

Did you ever find a fix for this? I'm having this same issue and can't figure out what caused it to start.

I've found the problem that causes this.

Instead of actually updating a record the event module deletes the record then creates a new one with the changes. This overwrites the unix time which is added by the event_views module.

I just added a call to the function that creates the unit time information to the update/insert handler and this fixed the issue.

I can confirm jmickela.

In my implementation I copyed the event_views_nodeapi() code from event_views.module in my own module, which is processed later than the delete/insert action within event_nodeapi().

is their a patch for this?

I need this patch too!!
Please!

I've just run into this problem as well, only it's working fine on one site but not another. I'm not sure how to track down the problem. I'd be happy to provide more info if it will help.

On one site, I can enter a new event or edit an existing one and the unix_event* fields are updated. On another site, the unix_event* fields are always set to zero.

Both sites are running Drupal 6, with a slight difference in versions. The site where it works has Drupal 6.20, the problem site is 6.19 (I know, I know - I'll update soon!). I don't see anything in the release notes for 6.20 related to this, so I don't think that's the issue.

both sites have the same versions of the relevant event modules:
Event 6.x-2.x-dev and
Event Views 6.x-2.4.

Any help would be great.

Thanks.

I found the solve:
My site was upgraded from D5 to D6, cause in the system table, the owner field was at the end.
I change the sort:
filename, name, type, owner, status, throttle, bootstrap, schema_version, weight, info.
...and the problem went away.