By conkhead on

Hello, all. I've had a weird thing happen when I try to install modules in my Drupal 4.6.3 installation: about half the time, when I go to the "modules" page in the admin to enable the module immediately after installing the module files on the server, the module page becomes unavailable - i.e., I get a browser "no-location-exists" error.

At first I just accepted this as a quirk; but it happens on about half the modules I try to install - and some of these I very badly want to use. (And yes, I have installed the module files on the server before trying to access the module page.) Has this happened to anyone else, or are there ghosts in my machine? (BTW, I'm running PHP version 4.3.11, MySQL version 3.23.53) My thanks in advance for any light anyone can shed on this --

Comments

moggy’s picture

moggy commented

which modules?

and which version? you have to match module version to drupal version, ie 4.6 to drupal 4.6.x.
cvs is a little different, some cvs modules still work in 4.6 but most have been updated for the immenent Drupal 4.7

Another possibility is that you're running out of memory when you install a new module. php only allocates a limited amount of memory to a process, 8MB on a typical install. Drupal can quite easily use more than that if you're using extra modules.

conkhead’s picture

conkhead commented

No, I have been making sure my module versions are right. But I was also beginning to suspect the PHP memory issue. I think I'm going to try increasing PHP memory - to maybe 12 or 24 MB - and see what happens. Thanks --

conkhead’s picture

conkhead commented

I think you're onto something re: out of PHP memory. I just found this: http://drupal.org/node/31819 - it's the exact problem I'm having. I'm going to mess with the PHP memory limit and I'll post my results.

conkhead’s picture

conkhead commented

Increasing the PHP memory, along with removing all the currently unused modules, seems to have worked. Thanks for the feedback.