I've just re-loaded or uploaded the latest Event Module. I have 2 entries in an "upcoming events" block which correctly display the number of days to go. Still though, when viewing each event as a normal post/node there is no reference to the Event Dates other than "Start 0 - 12:00 am" and "Timezone" with no value (see http://superjacent.net/cms/?q=node/624). When editing that particular entry, the Event Dates default to the current date. Clicking on the Calendar option at the bottom of the post/node appears not to be correctly hooked in, no month is indicated though the calendar displays without any reference to the event entries.

What am I doing wrong.

Comments

superjacent’s picture

superjacent commented

Could anybody at least have a stab in the dark, who knows it might point me in the right direction.

superjacent’s picture

superjacent commented

Updated again to latest version as of date 22 Aug 2007. Still the same problem.

superjacent’s picture

superjacent commented
Category: support » bug

Updated again to latest version as of date 24 Aug 2007. Still the same problem. Any feedback would be appreciated. Is this a known problem?

gerhard killesreiter’s picture

gerhard killesreiter commented
Component: Basic Event » Code
Status: Active » Postponed (maintainer needs more info)

Can you post the line in the event table that corresponds to your node?

superjacent’s picture

superjacent commented

Fields are:-
nid, event_start, event_end, timezone, start_in_dst, end_in_dst, has_time, has_end_date.

624 2007-10-07 00:00:00 2007-10-07 23:59:00 268 0 0 0 1
625 2007-07-15 08:00:00 2007-07-15 12:00:00 268 1 1 1 1
626 2007-08-19 08:00:00 2007-08-19 13:30:00 268 0 0 1 1
629 2007-06-30 08:00:00 2007-06-30 09:59:00 268 0 0 1 1
650 2007-07-28 08:00:00 2007-07-28 09:00:00 268 0 0 1 1
686 2007-09-09 08:00:00 2007-09-09 12:00:00 268 0 0 1 1
690 2007-09-25 18:30:00 2007-09-25 18:30:00 268 0 0 1 0

Above is copy/dump of all event table entries. Hope this helps.

superjacent’s picture

superjacent commented
Priority: Normal » Critical
Status: Postponed (maintainer needs more info) » Active

Does anybody have any clues on this.

shane birley’s picture

shane birley commented

This just happened to a site I have running with the event module. It just started happening without any warning, no patches or updates to this install of Drupal has been done since July. All of a sudden - BANG - the times display with Start: 00/00/ - 12:00am and the nodes no longer save date data.

There must be something I have missed but I just noticed this a few minutes ago. A bug in the date api, or views, or event. I am still checking into where the problem may stem from.

westwesterson’s picture

westwesterson commented

This is probably related to the bigger event views problem. Since event views itself is having problems displaying information, its no wonder that calendars which use views (and thus event views) don't work correctly either.

You may be able to start figuring out what is wrong by applying the latest patch in the event views issue:
http://drupal.org/node/147563#comment-316475

hope this helps

superjacent’s picture

superjacent commented

How do I apply the patch. Sorry for probably what appears to be such a simple question, but I've got no idea. Any help appreciated.

samuelet’s picture

samuelet commented

http://drupal.org/patch/apply

gerhard killesreiter’s picture

gerhard killesreiter commented
Status: Active » Fixed

The patch has already been applied to event_views so all you need to do is to download a fresh copy.

YOu will also need to save your views again.

gerhard killesreiter’s picture

gerhard killesreiter commented

Actually, there seems to be another problem: Your theme was not updated for event 5.2. There are a few suble changes between how the theme works for event 5.1 and 5.2.

http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/event/event...

here you can see most of these changes.

Mainly, you need to print $node->event['start_time_format'] instead of $node->end_time_format.

superjacent’s picture

superjacent commented

Thanks for the advice. As far as I'm aware I've got the latest Event (5.x-2.x-dev (2007-Dec-21)) installed.

Could you please elaborate on the "your theme was not updated for 5.2". I'm not a PHP person (yet) but I should be able to follow some simple instructions.

superjacent’s picture

superjacent commented

I've still got the same problem. I keep updating to the latest version of the Event module and still the problem persists. I've got no idea where to start regarding, "your theme was not updated for 5.2".

I've since changed themes, from Slash to Newsflash, still the same problem.

Any help appreciated.

Further, I've since created a few more events and checking the Recent Log entries reveals this:

Unknown column 'tz.is_dst' in 'field list' query: SELECT e.event_start, e.event_end, e.timezone, e.has_time, e.has_end_date, tz.offset AS offset, tz.offset_dst AS offset_dst, tz.dst_region, tz.is_dst, e.event_start - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND AS event_start_utc, e.event_end - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND AS event_end_utc, e.event_start - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND + INTERVAL 39600 SECOND AS event_start_user, e.event_end - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND + INTERVAL 39600 SECOND AS event_end_user, e.event_start - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND + INTERVAL 36000 SECOND AS event_start_site, e.event_end - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND + INTERVAL 36000 SECOND AS event_end_site, tz.name as timezone_name FROM event e INNER JOIN event_timezones tz ON tz.timezone = e.timezone WHERE nid = 758 in /mounted-storage/.................../drupal-5.6/includes/database.mysql.inc on line 172.

nid = 758 (is an event node).

Any clues please.

superjacent’s picture

superjacent commented
Status: Fixed » Active

I've just noticed that this thread is marked as fixed and is why I've probably got no responses. This post is merely changing the status accordingly. Please refer to #14 for issue/problem.

superjacent’s picture

superjacent commented

I'm now making headway. From post #14, I've established that the MySql table, event_timezones was missing a field, "is_dst". I've since added that column directly to the table as an integer type. My test on a local copy of drupal now appears to be working correctly except for the fact that my times are an hour out. Here in Australia we're in the middle of daylight saving time. When I enter a time of 13:30 hrs, it's displayed as 14:30 hrs.

Could somebody tell me what the precise attributes are for the field, "is_dst". All I did was 'best guess' approach. What values are stored in this field, I'm assuming 1 or 0 (true / false) type entries. At the moment, for me, there's no value, just null (nothing).

japerry’s picture

japerry
Location KOMK
commented
Status: Active » Closed (outdated)

Event for Drupal 8 is unrelated to older versions. If an issue similar to this one exists, please open a new issue with the 8.x branch.