By computerlarry on

I am running Drupal 6.1.3 with MAMP on a MacBook. I erased the drive before I started, and I haven't installed any programs except MAMP Pro.

I have been adding modules one at a time. I noticed that after having placed certain modules in the modules folder, as soon as I press Save configuration there is some work going on, and then afterwards, all I get is a blank screen. If I remove the module folder from modules, then I can see the existing modules listed.

Modules that have given me this trouble:
pathauto, swftools, ubercart, views

Each installed module folder has the same rights as the modules folder itself: Owner is _www, group is _mysql. Everybody can read, only owner can write, all can execute.

I really have gone through all the work of a clean installation so that I can use Ubercart.

Thanks.

Larry

⋅ Categories: Drupal 6.x

Comments

vm’s picture

vm commented

If the screen is blank, you are likely hitting your memory limit. Check php.ini, what is your memory limit set at?

The more modules you install, the more memory requried to run your entire installation.

computerlarry’s picture

computerlarry commented

16 MB wasn't enough for me, either. I've set it to 32MB. Is there a practical limit for this?

vm’s picture

vm commented

its dependant on the amount of modules you use and the amount of memory that can be used. Every combination uses a different amount of memory.

mrsimonelliott’s picture

mrsimonelliott commented

I had exactly the same problem on D6.13, I don't think it is memory related.

The problem occurred for me when I enabled RDF, Calais and CalaisAPI

However if I change the theme (it doesn't matter what to) I can see admin/build/modules but not admin/build/modules/list. After changing the theme and being able to see my modules list at admin/build/modules, if I try and view it at admin/build/modules/list the problem returns and I can not view it at either url. I have to change theme again, nb I can change back to the original theme or any other theme and the problem is resolved until I try and visit admin/build/modules/list

This is really strange behaviour.

English web designer in France Bantalabs

vm’s picture

vm commented

check your apache error logs to see if there is an error being printed.

mrsimonelliott’s picture

mrsimonelliott commented

Thanks VeryMisunderstood, it was a memory issue. I have increased php memory limit on my server from 32M to 96M and all is good.

English web designer in France Bantalabs