I'm not actually sure whether this is a problem of the event module or views. I only discovered it after installing views-5.x-1.5. Already installed and activated were event-5.x-1.x and eventrepeat-5.x-1.x-dev. Then, as soon as i tried activating views, drupal-5.1 would only (quickly) return blank pages for all admin pages accessed by the menus/links or by refreshing the pages in Firefox 2.0.0.2.

Some pages would appear if i accessed some admin pages by url, they appeared but they didn't seem to save any configuration changes. I didn't have time to determine any more specific behavioural pattern.

I then dropped all views tables from my database and deleted the views module folder and the admin pages reappeared. But when i tried to add an event, the event pages would blank on using preview or submit buttons.

I disabled eventrepeat and the events pages no longer blanked, but i could only get "Validation Error..." for the one event submission i tried.

Finally, i disabled event and things seem to be working normally again -- little consolation, since this site is primarily for publishing and managing events.

No relevant errors appeared in the drupal's logs.

Platform

(from my Status Report page, http://h0lug.sourceforge.net/cms-h0/?q=admin/logs/status:
Drupal 5.1

Database schema Up to date
File system Writable (public download method)
GD library bundled (2.0.28 compatible)
MySQL database 4.1.21
PHP 4.3.10
Unicode library PHP Mbstring Extension
Web server Apache/1.3.33 (Unix) PHP/4.3.10

Comments

ADMarshall’s picture

Category: bug » support

Admittedly, i'm not sure if i should be first posting this as an issue or first trying the support forums. Though, on second thought, i suspect the latter would have been best. My apologies if i slipped up on protocol. If i have, i'd be grateful if some admin could inform me of as much, so i can shift this enquiry to a better forum, then remove this posting. Thanks.

ADMarshall’s picture

Project: Event » Event Repeat

Disabling eventrepeat seems to resolve this issue. Still testing... (Patience, please. This is a new, initial installation of Drupal 5.1 -- still not sure what's causing what to happen when and where...)

ADMarshall’s picture

Assigned: Unassigned » ADMarshall
Status: Active » Closed (fixed)

False Alarm?

Setting the event content type to allow repeating events reduced the number of times blank admin pages appeared, but did not stop their occurrence.

It now seems this is more likely an issue with the quality of the network route between sourceforge.net and my box in SàiGòn, Việt Nạm.

Apologies is any event, eventrepeat or views users or developer were unduly alarmed or inconvenienced.

airblaster’s picture

Actually I have a very similar problem:
If I enable event_repeat or event_views, the Access Control page
( /drupal/admin/user/access ) delivers an empty page.

airblaster’s picture

Category: support » bug
Status: Closed (fixed) » Postponed (maintainer needs more info)

Forgot to re-open the issue

el_reverend’s picture

I do have the same issue. I am able to edit the event but after submitting it I am presented with a blank page, where the event detail should be. It will still create events, but with a wrong date and time (00:00).

seanbfuller’s picture

I can confirm this. Seems that it's a call to event.module's "event_date_later" function:

Call to undefined function event_date_later() in /mysite/sites/all/modules/eventrepeat/eventrepeat.module on line 82, referer: http://mysite/?q=admin/build/modules

Line 82 is eventrepeat's hook_cron(). Why this function suddenly can't be found is a mystery to me.

SpriteGF’s picture

Version: 5.x-1.x-dev » 5.x-2.x-dev

I'm confirming Sean's comment #7. Once I activate Event Repeat module, the module screen blanks out and I get the same error message. I'm using event version 5.x-2.x-dev and Event Repeat v 5.x-2.x-dev.

rmiddle’s picture

Need to confirm this is fixed.

Thanks
Robert

interfaced’s picture

same issue

oadaeh’s picture

Status: Postponed (maintainer needs more info) » Closed (won't fix)

This issue is being closed due to age and/or version. If this issue is still valid, please reopen it against the 6.x-1.x branch and update it. There will be no more follow ups against the 5.x branches.