CivicSpace will not install if php's memory_limit setting is less than 24MB. Drupal's docs, however include no such requirement, so I am getting users installing my module on their site and then having Drupal exceed the paltry default 8MB. Drupal does not error out in any obvious way from this problem (just a blank screen - doesn't even log to the watchdog log, since it's already out of memory), so the user is left clueless as to the source of their problem.

http://drupal.org/node/34510

Comments

cel4145’s picture

What specific documentation do you want to see this advice added to?

bslade’s picture

Re: where to add this info?
The "Tuning PHP" handbook page (http://drupal.org/node/2602) seems like a good place. Maybe add a pointer to the "Tuning PHP" page from the "System requirements" requirements handbook page? (http://drupal.org/node/270)

Ben in DC

chx’s picture

Sometimes 8MB is enough.

And Drupal 4.7 won't have memory problems if split gets in.,,

cel4145’s picture

So it sounds like we shouldn't make any changes at all at the moment until we see what happens with split?

boris mann’s picture

8MB works fine for a core Drupal install -- AFAIK, this doesn't need to be raised. It wouldn't hurt to add in a note that adding additional modules requires an increased memory_limit, and mention that CivicSpace requires 24MB with its load of modules.

sepeck’s picture

for now I added the a note about php memory requirements to http://drupal.org/node/270. If this is sufficient, then please close this issue.

bslade’s picture

Will "split" (only call functions & allocate mem for them if they're needed?) be part of the default installation?

It's tough when people pick generic words for functions/modules/software because it makes it impossible to search for info about them. Where is a web page for split?

sepeck’s picture

Blame the php developers
http://drupal.org/node/34694

I can't say where on their site it is, but there's the source of it.

seanr’s picture

Sepeck, that page is fine, but I think the installation instructions should mention it as well. Something explaining that the modules page or the access control page loading only a blank screen after adding new modules may be related to insufficient memory. PHP/Drupal does handle that cleanly, leaving users in the dark if they've never read about it or encountered it before. I recommend adding it to this (and INSTALL.txt) in the Optional Requirements section:

http://drupal.org/node/260

sepeck’s picture

Status: Active » Closed (fixed)

/requirements page updated.