admin/build/modules displays a blank page. This was never a problem before for my site. The most recent module I've added is the admin menu. A search indicates that this can result from the hostserver's PHP limit being too low. My host is Hostgator, the limit is 64M. From the information I found in the Hostgator forums, it looks like this is a major cost upgrade to get increased. So, I'm wondering how I know if this is indeed the culprit?
I have 49 modules installed. I can provide a list if that helps (?). One of the modules is Gallery with g2 image....I read somewhere that it could hog the PHP, but I don't know enough about PHP to know if this is accurate.
Is there another reason besides a too low PHP limit that could cause the modules page to come up blank?
Any other info. I could provide to help figure this out??
Any help/advice would be greatly appreciated!
Comments
That is usually what happen
Did you try the suggestion here: http://drupal.org/node/31819?
Yes, and...
It was that post that alerted me to a possible PHP memory limit. So, I ended up deleting some modules (3) from my cpanel that I knew I wasn't using. I was afraid to delete any more, since I couldn't access my Modules page to disable them first. Then I also checked my Feed Aggregator and saw that there was one with an update interval of every 15 minutes, and the other three were set for 2 hours. I changed these to 2 days. I don't know if that has anything to do with it, but it was worth a try.
Now my admin modules page is back and all seems to be well again. Do you think the Feed aggregator could have been the root of this problem, or was that just a coincidence?
Sorry. I don't use that
I don't use and I have never tried that module so I don't know how it behaves. I am sorry that I can not help you a lot on that.
I had that problems only when
I had that problems only when my limit was too low.
Is 64 MB considered low?
I'm not sure what the "standard" would be for webhosts, so I'm not sure if 64 MB is reasonable or not. My host, Hostgator, states that to increase it over 64 MB would require an upgrade to a dedicated server, which would cost $174/month at the lowest option. Obviously, this is a lot of money for a single Drupal website and I cannot afford it. This is why I'm wondering if other things are going on that cause this error, and perhaps if it is not the fault of the PHP limit.
oboskovic - what was your limit when it was too low? Approx how many modules did you have at the time?
To be honest, I don't
To be honest, I don't remember. But think that 64MB was enough form me, always.