Functions.php on Twentyten child theme causes blank pages (MU setup)

I’ve resolved this by making sure no extra returns or lines are on the page after the last closing php tag “?>” in your functions.php file

It just doesn’t like extra spaces/lines after it closes a function.

Hope that resolves your issue!

@bionicsquid , link to the problem? Want to paste your functions?

The problem may actually be that there are blank lines in the file and redirection won’t handle it well.
http://www.cyberciti.biz/faq/php-redirect/ explains how they may interfere with any redirection code.

Note that blank lines that are between <?php and ?> tags don’t make a difference: php preprocessor cleans them out before the http protocol level redirection takes place.

This is also why New Nine Media’s fix works sometimes: the editor may trim empty lines from the end of the file. It won’t help with lines that are in the middle of the file though.

Although I have changed headers a few times I now am getting the following error codes:
Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 12288 bytes) in /home/leanonme/public_html/wp-includes/media.php on line 253
And the other one is a security issue

Does any one know about this…and how to fix it.

Thank you,
rdf

Bump on this question. I get the white screen with a single line functions.php. Absolutely no extra line feeds, carriage returns, etc. I tried deleting the file and putting a new one (again without extra lines) with no effect.

<?php add_filter(‘widget_title’, ‘do_shortcode’); ?>

When I go back to anything after the white screen, it seems to have been updated, but it happens all the time with many different parts of wordpress after functions.php is added to the child theme.

Anyone have an idea?

I haven’t worked on that site since the recent WP upgrade. However, with the previous version I was never able to find a solution and just had to do things without functions.php. Maybe this bump will bring in somebody with some insight.

If removing the ‘functions.php’ file from your child theme means you no longer see the WSOD, then definitely there’s a problem with your child theme’s ‘functions.php’ file. It might be, as some have pointed out, a simple matter of white space or empty lines. Or it could be that your code is incorrect (eg. a missing php end tag or possibly one too many). Or it could be that you’ve missed out on something, such as removing an action hook belonging to the parent theme and replacing it with a new function. I got the WSOD when I neglected to remove_action('widgets_init', 'twentyten_widgets_init' ); before defining new widget areas in my child theme’s functions. Remember that the child theme’s ‘functions.php’ always loads before the parent theme’s functions.php. Whether your installation is a single WordPress or MU or Multisite, the same rule applies. If your child theme’s ‘functions.php’ file is blank or empty, then it shouldn’t be there.