There was a small bug and some dead code in the event module's nodeapi function. It appears that the update_event script may have failed to successfully configure the flexinode created for the default event type. That is, flexinode-1 was given the 'all' calendar view when really the flexinode-x should have been given the 'all' calendar view, where x equaled the id of the event flexinode created in the update script.
Since the view was not set, the event node did not show up in the calendar. Furthermore, some users mistakenly created nodes of the event type. Since these nodes were not configured correctly the times were not entered into the database and upon correcting the configuration the nodes failed to update because the update database call. There were also 2 variables unused. . .
| Comment | File | Size | Author |
|---|---|---|---|
| event_update.patch | 1.5 KB | dtan |
Comments
Comment #1
killes@www.drop.org commentedno longer relevant