By jaypan on

I just installed the devel and coder modules into my local drupal installation. I have run into a problem.

I have my memory limit set at 64M in my php.ini. Yet I get this error at the bottom of administer -> site building -> modules:

Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 2330761 bytes) in C:\wamp\www\drupal-6.2\includes\common.inc on line 2275

So I bumped my memory up to 128M (which I can't see that I should need), and I get a blank screen.

I'm still pretty new to drupal, so I really don't know how to fix this issue.

⋅ Categories: Drupal 6.x

Comments

Iumentum’s picture

Iumentum commented

Try to raise the max_allowed_packet in the mysql config file!

AndrejT’s picture

AndrejT commented

What can I do, if I cannot raise the max allowed packet in MySQL configuration? M&y provider says it is not posible.

vm’s picture

vm commented

The only thing you can do at that point is get a new provider that allows you to change those settings. Or get a VPS or Dedicated solution that allows you to change default settings on the server.

tryitonce’s picture

tryitonce commented

AndrejT,

you can try this:

Install one module at a time. Be patient and try again if it did not work.

When you hit the "save" button after the installation and you get a white screen (http://www.example.com/admin/build/modules/list/confirm/ - wait a moment and then go to the .... /module/list page to see if the module did register. Try not to use the back option on your browser - make a fresh approach to the admin page for the modules (http://www.example.com/admin/build/modules/list/) or even one step back via (http://www.example.com/admin/build/modules/) .

You should also check http://www.example.com/admin/settings/performance - make sure cache is off and clear the cache. Also clear then the cache of your browser.

Another reason my also be a slow connection to your Host provider and you get timed out after hitting save following the activation of the modules you need. In this case try a little later or at times of the day (or night) when there is not so much demand on your host. This also seems to be a more frequent problem with free host accounts. On our payed for accounts we rarely have this problem. If we get a blank screen there, then it is usually a problem with the module (blank spaces or similar).

Good luck