WordPress MU

Dear all,

I have got this error message on signup register step.

How can i solve it?

Warning: Cannot modify header information - headers already sent by
(output started at /home/httpd/vhosts/httpdocs/wp-content/themes/home/header.php:7)
in /home/httpd/vhosts/httpdocs/wp-signup.php on line 347

many thanks in advance.

magi

i can't resolve this error. can anybody help me.

There's whitespace at the end of the file. This has been covered in many, many threads.

i can't find any white space at the end of file.

printf(__("The blog you were looking for, %s doesn't exist but you can create it now!"), $newblog );
}
break;
}
?>
</div>
---- ??? You Means here???
<?php get_footer(); ?>

Line 347 :

header( "Location: http://{$current_site->domain}{$current_site->path}" );

Why it happen on my site? I want announce to start the blog service to my community.

Many thanks in advance.

Magi.

Do you get this error when you hit the link "create a new blog"?

If so I think I found a potential answer to this problem

Did you edit any of the following fields?
Banned Names:
Limited Email Registrations:
Banned Email Domains:

If so please check for trailing spaces - meaning make sure you don't have a blank space at the end of your entries

The line 347 error points to an array for illegal names and I think this was my problem and may be what is happening with yours....

Good luck
AJ

Also I only noticed this error wp-signup.php on line 347 when using IE - my firefox browser had no issues

I was able to replicate the error by adding a space to the end of my BANNED NAMES list and I got the error. I removed the space and the error didn't appear so that is a good place to start

AJ, You're a genius! I've been trying to figure this one out for a while. On a new install I'd made a truck load of changes. I'd undone nearly all of them and I certainly wouldn't have spotted that trailing space, it's hard to see even when you're looking. This fixed my wp-signup.php redirecting to root problem. THANKS

glad to help - hate those silly errors that destroy your fun!

:)

I got this problem today.. which is odd as I'm sure I have never added a space onto the end of the banned names list. I guess the banned list needs a strip wrapping round it

FYI: having errors printed to the screen in a production environment is a security concern.

Indeed it is - whats why my php errors go to /tmp/php_errors

MU is setup to dump them into an 'error_log' file if you have one created within the root of your install and it's writable by the server. Darn cool having it there if you ask me. :)