Closed (fixed)
Project:
Drupal core
Version:
4.6.0
Component:
base system
Priority:
Normal
Category:
Support request
Assigned:
Reporter:
Created:
5 May 2005 at 18:44 UTC
Updated:
10 Nov 2005 at 16:00 UTC
I'm doing an intranet installation of Drupal (so it's behind a firewall and can't be shown).
I was running the site on a test server and just moved it over to the permanent server. Everything works fine except one thing that I can't figure out.
When logged in as the administrator, the Modules link doesn't work. When clicked, the browser tries to load a page and then stops, leaving me on the original page.
I've tried removing all modules and starting over, but that hasn't helped.
Any pointers?
Comments
Comment #1
killes@www.drop.org commentedYou are talking about admin/modules? Check the memory setting for php. All modules get included on this page, whether they are enabled or not.
Comment #2
agentrickardYes, sorry, forgot the link
admin/modules
So you're saying I could be hitting a memory buffer limit?
The new box does have a different PHP install. I'm not a sysadmin, but I'll check it out.
Comment #3
agentrickardnoob alert: Checking to make sure I'm running down the right path.
What is the memory_limit setting that is appropriate?
These settings work for my test machine:
/usr/local/php/lib/php.ini
;;;;;;;;;;;;;;;;;;;
; Resource Limits ;
;;;;;;;;;;;;;;;;;;;
max_execution_time = 30 ; Maximum execution time of each script, in seconds
max_input_time = 60 ; Maximum amount of time each script may spend parsing request data
memory_limit = 8M ; Maximum amount of memory a script may consume (8MB)
If so, I'll have to ge the sysadmin involved.
I also looked in the Drupal Handbook (http://drupal.org/node/270), but didn't find an obvious answer
Comment #4
killes@www.drop.org commented8 MB isn't enough if you are going to need a lot of modules. if you don't need them, you might get away with not only disabling them but to remove them from the modules directory.
Comment #5
agentrickardFigured as much, but I'm going to have to get professional help on that. I've never tweaked those settings on my test server and have run drupal 4.5 and 4.6 successfully.
The site I'm trying to diagnose now is a straight port from one server to another (albeit one with different settings, I'm sure).
Thanks for the pointer. Maybe something should be added to documentation.
Comment #6
agentrickardI'm going to open this back up. I checked the PHP settings for the new server, and they are identical to those posted above. So it seems that changing the memory limit isn't an issue here.
I've been methodically removing modules and have noticed that the links breaks when the block.module is present in the modules directory. If I delete block.module, then the admin/modules page loads. Of course, if I do that, then I lose my navigation rails.
So I need block.module (it's core after all!).
For the moment I'm working around this by manually switching the system table in MySQL for each module from 0 to 1 if I want to toggle a module on/off.
Any other debug thoughts?
Comment #7
thorfinn@kerneltrap.org commentedhi
I have this in my production system at http://abbotsford.sca.org.au/stormhold/ which is a 4.5.2 box and on my test box which is 4.6.0.
Comment #8
thorfinn@kerneltrap.org commentedI removed the latest addition to my test system
fontsize and several themes blix, gworks et al
without effect and enacted blog through webmin
on the system tabl, and now it works, now turned
blog off and there was a system reboot as well.
Note to self, doing far too many changes between
testing, is poor practice.
Thorfinn
Comment #9
agentrickardThis issue has been addressed in the documentation http://drupal.org/node/31819.
The applied fix:
inserted into my settings.php file has fixed the issue.
+1 to the Drupal handbook!
Comment #10
(not verified) commented