By speakpoetic on

I was adding an About Page and creating fields. All was working fine. I then went back into Administer and the page comes up blank while showing 'Done' loading. How can I restore this page so I can administer the site? What could cause this?

⋅ Categories: Drupal 5.x

Comments

ultimike’s picture

ultimike
Primary language English
Location Florida, USA
commented

Try clearing the page cache. This can be done with the devel module or by doing a "delete from cache" on your drupal database.

-mike

P.S. Since you can't get into the admin area, the devel module probably won't help you - gonna have to go with the 2nd option.

speakpoetic’s picture

speakpoetic commented

Thanks Mike...cleared out cache every which way I could to no avail...any other thoughts?

GC Wood
http://speakpoetic.com

ultimike’s picture

ultimike
Primary language English
Location Florida, USA
commented

GC,

Hmmm - this is an odd one assuming that before you added the new page, everything was fine, then after you added the new page, the admin area wouldn't appear.

If you're using 4.7, sometimes if you have lots of modules in your modules directory, PHP can run out of memory loading all that code - but usually only on the admin/modules page. When that happens, the page goes blank - sounds familiar to what is happening to you except it is on any admin page, correct?

If you have access to it, try upping the memory that PHP has access to (in the php.ini file) to 32MB.

-mike

speakpoetic’s picture

speakpoetic commented

Mike,

Upped the memory and nothing. However, if I go to the url admin/settings or admin/content it comes up but admin...admin/logs...admin/help, etc. does not...interesting. I'm running 5.x Drupal... This is quite strange...any other thoughts?

Thanks again for trying to help me through this!

GC Wood
http://speakpoetic.com

speakpoetic’s picture

speakpoetic commented

Mike,

I just disabled View UI and now administer shows up. Can you imagine that to be the problem and if so, any ideas why it would cause the problem?

GC Wood
http://speakpoetic.com

styro’s picture

styro commented

for an actual error message. If this is on a development or test server, it might also be useful to configure PHP to output the error messages to the browser as well.

--
Anton
New to Drupal? | Forum posting tips | Troubleshooting FAQ

ultimike’s picture

ultimike
Primary language English
Location Florida, USA
commented

With Drupal 5, memory shouldn't be an issue with the admin/modules page due to the new .info files.

I haven't used the views module with Drupal 5 yet, so I'm afraid I'm all out of ideas. Sorry.

-mike

globefox’s picture

globefox commented

Try accessing the admin via

http://www.weallreuse.com/?q=admin/settings or

http://www.weallreuse.com/admin/settings

this works for me and I was able to check cache settings etc and check modules.

I have also cleared the cache and the sessions tables in the DB.

I still find the missing /admin page issue a bit scary and have not been able to fix it.

suggestions and comments welcome

speakpoetic’s picture

speakpoetic commented

Thanks globeFox,

I can get to some of the sub pages but not others. Seems each time I can access fewer and fewer. I'm sorry you are having the same challenge but I am glad to know it's not just me...clearing cache today did not help...don't know what to do now...thinking of dumping the entire thing but I really like so much about it...this is eating away at my time and knowledge so quickly though!!

GC Wood
http://speakpoetic.com

kvarnelis’s picture

kvarnelis commented

I had this very problem today. I deleted the views module and everything is fine now, except for my lack of the views module...

Reenabling views killed the page again. After a while, all pages began dumping this at me:

warning: _phptemplate_render(.//block.tpl.php)

along with some other information which regrettably I did not save and cannot retrieve anymore.

I am observing that the server we're running on is very overloaded. So it could be that the errors views is causing are demanding overhead from your server that it isn't able to provide.

Macint’s picture

Macint commented

yes i fixed by removing a module but not the views module i removed the image module and the admin page works fine.

but when i ad it again it goes blank again :(

Steven Vermoere’s picture

Steven Vermoere commented

I've had this also with a CCK module Date. I've been running Drupal Update Status on my site. After running an update of the CCK modules and update.php, I got a blank administration page.
Happily enough, I saw some errors from CCK Date module flashing by when doing update.php. I removed the date-module, replaced it with the most recent version and everything was working again.

Very scary when it is happening and it is not always possible to see wich module was causing the error. perhaps some-one can develop a php-script that reads the logfiles and gives the error, so that it can be executed and analysed.

Macint’s picture

Macint commented

i installed the imagecache module and it went blank again i took away the poll module and it works.

it seams like there is a max amount of modules you can have.

plz help!!!!!

Macint’s picture

Macint commented

no sry it wasnt like that

just ignore this and what i sent before

BUT THIS IS RLY ANOYING!!!!

aiwilson’s picture

aiwilson commented

I get the "white screen of death" when I enable the views module with the simplenews module enable. If I disable the simplenews module, then the views module works fine. Hope this helps.

A
W

vm’s picture

vm commented

simple news and views work just fine together, I use them both. The problem you are having is that you server needs to have more memory alotted to your account.

The more modules you install on your drupal, the more memory you need for your drupal to run.

each module uses a different amount of memory.

WSOD's are apache errors and most times when you check the apache error logs you will see a memory exhausted error.
_____________________________________________________________________
My posts & comments are usually dripping with sarcasm.
If you ask nicely I'll give you a towel : )

aiwilson’s picture

aiwilson commented

I tried to enable the views module and got the white screen. So, I arbitrarily disabled a module and the views worked. However, I got the white screen again when I enabled the views-ui module. So, once again I arbitrarily disabled another module and the views-ui enables just fine. Seems like I can only have 9 modules enable (excluding the core modules). I get the white screen every time I try to enable the 10th module, regardless of the module.

The memory configuration definitely explains this limitation. I checked the /var/log/apache2/error_log and found the memory exhausted error.

Thanks,
A
W

vm’s picture

vm commented

increase the memory_limit in php.ini

_____________________________________________________________________
My posts & comments are usually dripping with sarcasm.
If you ask nicely I'll give you a towel : )

kcease’s picture

kcease commented

My entry over at the thread "Blank page randomly but frequently" might be helpful. The bottom line, at least for my blank page problem, is that PHP was running out of memory and needed its available memory bumped up.

calebtr’s picture

calebtr commented

I was getting this problem after adding a few new functions to a custom module. There were no errors in the Apache logs and none on the screen, though it's possible that's my configuration. There were no errors in the watchdog table. None of the above worked, so I tried running the module on the command line, and no dice again.

It turned out I had left out empty parens in the function declarations and this caused Drupal to peter out on anything except the front page. That's what I get for remembering Perl better than PHP.

Is it possible Drupal 5 is not reporting PHP errors - I would hope a misdeclared function would be mild enough to make it into watchdog - or is this really a configuration thing?

jeannine’s picture

jeannine commented

i was also having this problem all week. I made the changes in php.ini file, i cleared the cache, i deleted new modules, there were no errors in the logs. but still it wouldn't i was at a loss. Finally it dawned on me to restart the server and then everything was fine.

aangel’s picture

aangel commented

Yep, this was happening to me on a fresh install on my dev box...restarting the server did the trick.

Andre'

popicon’s picture

popicon commented

So, I'm new to Drupal and I went module crazy. I installed *everything* I thought I would ever want. Well, as it turns out, many of the modules have been problematic. My biggest issue was that the page at "url"/?q=/admin/build/modules would go BLANK. I freaked out a little when it first happened. In the beginning, I was selecting more than one checkbox at a time and then saving. This became a problem because I didn't know which of the modules was causing the problem. Now, I just do one at a time. It's a PITA, but it's been better and more successful.

The other trick is that if the screen goes blank I can, most of the time, use the browser's 'back' button to return and undo the problem. If that doesn't work, you can always go to the module install directory (I use "document root"/sites/all/modules/) and just 'rm' the directory of the module you just tried to setup. When you reload your admin page, you will see it in all of it's glory again. If you really need it, you can re-install it. It's not like it's hard to untar or anything. I have found this *always* does the trick.

Good luck!
Nathan Schmidt

janvangorp’s picture

janvangorp commented

was a memory problem...

http://drupal.org/node/31819

Richeh’s picture

Richeh commented

A much easier way of fiddling with enabled modules; use your SQL browser, or PHPMyAdmin, to open table
yourDrupalDatabase/system
it'll list all the available modules and themes. find the module you just enabled, and switch "1" (on) to "0" (off) in the "status" field, and when you refresh your drupal site it'll be deactivated, but still installed.

acquiel’s picture

acquiel commented

Hi - Did a fresh 5.x install and switched to an uploaded theme. Then, all I did was turn on several of the default modules. Next thing, the admin page is blank. I've made no other modifications. For me, the problem was NOT memory, or custom modules.. Remember - this is a clean install...

After fiddling around a while, found these two issues (the first un-related, but important to note).

1. Statistics module is incompatible with caching (found error message under site configuration)

2. Tracker module causes the blank admin page... Disable Tracker, and viola'! Admin page returned.

I'm new to Drupal, and will do some looking for the proper place to post bugs... but in the meantime, FYI, a clean install (Linux/PHP5) may have incompatibilities with the default Statistics module (when caching is enabled) and the default Tracker module may cause the admin page to go blank.

Best regards,
T

lafo’s picture

lafo commented

My problem was that *SOME* admin pages plus the user profile pages were blank. The solution to my problem was disabling the Captcha module.

Richard Laffers
laffers.net

philk’s picture

philk commented

When I enabled a different theme as default, everything went blank, so I dumped and reloaded the db to get it back working in the old theme. Then for a second attempt I just copied everything in the new theme and pasted it over everything in the old theme. Now the front page works but nothing else.

After sifting through all the similar problems the common solution is not enough memory. We have ran into this before but usually all sites crash or the Apache system admins are alerted some how and notify me. I believe we have 64 available for memory so I don't think this is the issue.

Any thoughts?

Thanks

bennebiest’s picture

bennebiest commented

I had the same problem (blank admin page).
Disabled the automatic updates solved this issue.

source: http://www.tmsnetwork.org/blog/content/2008/08/22/drupal-6-slow-administ...