I'm having a lot of problems getting modules to install properly with my Drupal site.

I'm running everything on a local test server with MySQL (5.1.34) and PHP (5.2.9-2), and I have the following modules enabled:

CCK:Content

CORE:Comment
CORE:Database Logging
CORE:Help
CORE:Menu
CORE:PHP Filter
CORE:Profile
CORE:Search
CORE:Statistics
CORE:Taxonomy

DATE/TIME:Date API
DATE/TIME:Date Timezone

IMAGE:Image
IMAGE:Image Import
IMAGE:Image Attach

OTHER: FCKEditor
OTHER: Webform

VIEWS: Views

I only have about 30 different nodes worth of content, and I've only been working on the site for a few days. I assumed that I was encountering the memory problems that have been posted on this forum frequently, but I've increased the memory available in the php ini file and restarted the server multiple times. I'm currently running 1024mb of memory which is absurdly high for a site with almost nothing on it.

Whenever I try to enable a module like the "Date" part of the date module, I get a blank confirm page, and after navigating back to the module page from the admin page, the Date section remains unchecked. In fact, installing any new modules leads me to a blank page where I then have to go back to the admin page to see if it worked or not.

I'm trying to set up a site that can store a large number of events and have users sign up for those events and be able to see a calendar of their scheduled events, so those modules and their functionality are an absolute must. Specifically Views, CCK, Calendar, and Date.

Any tips or information would be excellent. I've searched the forums for a similar issue that was unresolved by increasing php memory, but I came up dry.

Thanks in advance.

-Red

Comments

reddyenumber4’s picture

Priority: Normal » Minor
Status: Active » Closed (fixed)

I went through the PHP error logs and lo and behold, the problem was with execution time. It didn't matter that I had enough memory, or that things were slowly chugging along. It mattered that they were chugging so slowly that the script timed out.

A quick change to php.ini did the trick.

Glad I only wasted my own time.

Cheers,

-Red

pete_dr’s picture

"It mattered that they were chugging so slowly that the script timed out" ... what do you mean?

"A quick change to php.ini did the trick" what exactly did you do? because i'm getting blank screens left and right then errors. in the past i'd get the memory error telling to me increase the memory in php.ini but never blank pages. share your solution please? :)