hi,

i have a strange problem, very serious,

after submitting a blog or story node, drupal returns a blank page, not the submitted node,
i upgraded from 4.7 to 5,

please help me,

Comments

uzbekjon’s picture

Hi enky4u,

Sorry for unmeaningful comment, but I read some forum topics several days ago regarding this issue. Don't know if they have resolved it, still good idea to check out the forum or issue tracker.

And yeah, try to install Drupal 5.1. Lots of bug fixes. So the problem might have been resolved.

Uzbek

-------------------------------
Sites for uzbeks and Uzbekistan:
Uzbek Lyrics Database
Uzbekistan Forum

enky’s picture

thanks uzbek,

i already upgraded to drupal 5.1,

hope the issue is solved soon,

my site is live, and user submissions are getting posted twice, :(,
as users refresh the blank page,

enky

jeeves’s picture

Drupal had been rock solid until upgraded from 5.0 > 5.1. Now, I too am suffering from the blank page after submitting nodes problem.

Thats the only change I have made recently, no new modules or anything.

siliconmind’s picture

usually the "white screen of death" means that your script run out of memory - maybe this is your problem? check server logs (if you can), try adjusting memory limit (if it's possible) or try disabling some of your modules to reduce memory use so you can check if memory is the problem.

enky’s picture

i checked the logs, there are no memory limit warnings,

markcheng’s picture

this is probably the most common and overlooked cause of drupal's white screen of death! I got this when making a small change to my new theme's template.php file. I'd get white screen after almost any type of form submission, then after hitting reload on same url, i'd get this type of error:

Warning: Cannot modify header information - headers already sent ...

it turns out in my template.php i had a lines of code like this:


some php code...
?>


<?php
...more php code

i was copy and pasting code so didn't care about needless close and opening of php, once I joined them, the problem went away...I read on another php site that the additional blank spaces before and after php open and close tags can throw errors. Dunno why but removing them worked for me!

hope this helps someone!!!

mc

Xangis’s picture

Thanks for posting this. I had developed a custom module and was getting the same bizarre problem and couldn't figure out why. You saved me a lot of head-scratching and frustration.

marcobravo666’s picture

your comment was very useful!

i typed and deleted some part of the code and that was what was creating me a lot of problems...

thanks for that...

mb

cburschka’s picture

http://drupal.org/node/111697 (which got ignored...)

I suspect mine is a cache problem: Pages work the first time round, come up blank when reloaded.

How long do your blank pages take to load? I

* If it's almost instantaneous, you probably have a caching problem too.
* If it takes a few seconds, it's a PHP error - check which modules you installed recently.
* If you're waiting for up to a minute (or several) for the page to load, it's a memory or runtime limit problem.

enky’s picture

thanks Arancaytar,

it seems to take some time, not instantly,

so, its cache problem, right?

i enabled cache in the performance settings, is this the reason?

enky

notarealperson’s picture

I'm having the same issue with a fresh install of 5.1.

ugh.

smither’s picture

I have a similar, but not identical problem with a new 5.1 site. Today I got brave and tried adding some modules. With several of them, for example the weather module, after the module is enabled all I can get is a blank screen. I need to remove the module from modules/ and restart Drupal.

The page is indeed blank - doing "view source" in Firefox (1.5) shows:

<html><body></body></html>

Any suggestions most welcome!

Thanks.

smither’s picture

In looking for related problems I found another thread (http://drupal.org/node/124731) which had this suggestion:

Add:

<FilesMatch "\.(php|html?)$">
php_value memory_limit 32000000
</FilesMatch>

to the .htaccess file.

I added the above to the .htaccess file at the root of my installation and it seems to have fixed my problem.

Hope this helps.

jgoge’s picture

I had the same problem:
Description: A blank screen appears in admin option, when a user login.
The problem: I made a mistake, adding a wrong release of module, it had to be for drupal 4.7, and the module was for the drupal 5.x.1.
Solution: replace the module for the correct one.

Saludos!

manic78’s picture

I ran to this issue more than once. It seems like the theme engine cannot parse/use theme/php files, especially template.php if it is saved as an UTF-8 file (starts binary with hex values: EF BB BF).

Wierd, but this is happening when a user wants to submit any kind of form, luckily the first experience is with the user login form :(

I think it is a serious issue, besides prevent non-english developers to write custom modules on their own language only! If you save your module with ASCII encoding you lost all of your accented characters. In my case I made a small module for non-english speakers only (I didn't want to provide information in English and than translate it to my language just to keep the normal way of this), but there's no way to show text with accented characters directly from a module.

So remember: Do not use UTF-8 file encoding for template.php!

Any idea how to cheat this?

zanematthew’s picture

not sure if this was resolved but i had the same problem, everyone said maybe a installtion problem, maybe a memory problem, etc. but i knew it wasn't those becasue my other drupal themes worked just not my CUSTOM drupal theme,

the resolution:
no closing php tag in template.php !

so i went thru bluemarine, graland, etc. line by line file by file and compared it to mine to see if i had a syntax error (my php isnt that great) and sure enough i noticed that in the template.php file there is an opening php tag <?php but no closing tage ?>

so your php template should look like this:

<?php
function () {
    some code here
}

but my question is why no closing php tag in template.php?

cyberDJ’s picture

I have the same problem and after i disabled Token module, my pages worked correctly :| Saddly without this module i can't use pathauto, but hey, it's more important to have a functional site :)

LiquidWeb’s picture

I used to use UTF-8 to have localized block areas and i had same problem too. Then i opened the file in the builtin editor of my FTP client I saw some weird chars as manic78 explained. Then I deleted those chars and my site works like a charm.

Cranked’s picture

hey there.. i was just looking for a solution as i had the same problem

then when i read about the

?>

<? php

solution, i figured i had 3 blank linkes after the php ?> closing tag at the end of my template.php

i removed them, and guess what ? the blank page issue no longer exists....

Vidarls’s picture

I was allso searchin for a solution to this, and removing empty lines after the closing php tags in template.php solved the problem.

masscrash2’s picture

Thanks for all the help guys this also fixed my problem by just removing the white space in between 2 blocks of PHP code.

Miguel_FM’s picture

My white space was one at the very top of the page before "php." It gave me a header already sent error - /home/example/public_html/includes/common.inc on line 314.

adampasz’s picture

FWIW

achilles_cheskonov’s picture

I faced the same problem .. it was showing a blank page after submitting the login form. I found one extra line at the top of the template.php page just before the <?php tags starts. Deleting the extra spaces solved the problem for me .

tsavino’s picture

I went into Administer › Site configuration>Performance turned on "Normal (recommended, no side effects)" ang got the The White Screen of Death can not get to any of my site. Does any body know where in the database I can turn it off? Looked everywhere and there is no fix to this problem that I can find all I want to do is turn it off in the database.

tsavino’s picture

Went through a data base dump found the the way to turn it off temp fix.

mschoone’s picture

This work for me in drupal 6.6

2dareis2do’s picture

no closing tag. Seems that you have to omit the closing tag in template.php. I had the same problem and removing the closing tag got rid of the blank page.

Not sure why this is the case but hopefully will help someone else.