The MU forums have moved to WordPress.org

Works - But can't create/add new blog (20 posts)

  1. alaskanbob
    Member
    Posted 16 years ago #

    Get this error at http://allalaskans.com when trying to add new blog

    Warning: Cannot modify header information - headers already sent by (output started at /home/mbgoirij/public_html/wp-content/themes/default/header.php:5) in /home/mbgoirij/public_html/wp-signup.php on line 347

  2. alaskanbob
    Member
    Posted 16 years ago #

    Did I not give enough information for my problem? Is this addressed somewhere in the FAQ or ReadMe.txt that I've missed?

    Can anyone give me a clue where to start looking please?

    Bob

  3. andrea_r
    Moderator
    Posted 16 years ago #

    Nope, there's nopt quite enough info, sorry. Here's my guess. :)

    Check for whitespace at the end of wp-signup.
    Is this a fresh and clean install?

  4. alaskanbob
    Member
    Posted 16 years ago #

    thanks andrea. Yes, fresh and clean install... about the fourth one actualy. What more would be helpful to know?

    I'll check wp-signup.

    Bob

  5. drmike
    Member
    Posted 16 years ago #

    Covered in the codex as well as previously.

  6. alaskanbob
    Member
    Posted 16 years ago #

    thanks drmike. I seem to be making progress. The blogs are getting created and work properly despite the error messages.

    I have new errors now when trying to create a blog.

    "Warning: Cannot modify header information - headers already sent by (output started at /home/mbgoirij/public_html/wp-content/themes/home/header.php:5) in /home/mbgoirij/public_html/wp-signup.php on line 347"

    If I understand correctly what I've read, then I should fine my problem at line 5 of this header.php file(Title Tag) I uploaded a new copy as suggested. What am I missing or misunderstanding?
    '<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
    <html xmlns="http://www.w3.org/1999/xhtml">

    <head profile="http://gmpg.org/xfn/11">
    <meta http-equiv="Content-Type" content="<?php bloginfo('html_type'); ?>; charset=<?php bloginfo('charset'); ?>" />

    <title><?php bloginfo('name'); ?> <?php if ( is_single() ) { ?> » Blog Archive <?php } ?> <?php wp_title(); ?></title>

    <meta name="generator" content="WordPress <?php bloginfo('version'); ?>" /> <!-- leave this for stats -->

    <link rel="stylesheet" href="<?php bloginfo('stylesheet_url'); ?>" type="text/css" media="screen" />
    <link rel="alternate" type="application/rss+xml" title="<?php bloginfo('name'); ?> RSS Feed" href="<?php bloginfo('rss2_url'); ?>" />
    <link rel="pingback" href="<?php bloginfo('pingback_url'); ?>" />

    <style type="text/css" media="screen">
    #page { background: url("<?php bloginfo('stylesheet_directory'); ?>/images/kubrickbgwide.jpg") repeat-y top; border: none; }
    </style>

    <?php wp_head(); ?>
    </head>
    <body>
    <div id="page">

    <div id="header">
    <div id="headerimg">
    <h1>/"><?php bloginfo('name'); ?></h1>
    <div class="description"><?php bloginfo('description'); ?></div>
    </div>
    </div>
    <hr />`

    Also this is a new error I'm getting when I add a blog from http://allalaskans.com/wp-admin/wpmu-edit.php?action=addblog

    WordPress database error: [Table 'mbgoirij_wordpress.wp_3_options' doesn't exist]
    SELECT option_value FROM wp_3_options WHERE option_name = 'blogname' LIMIT 1

    WordPress database error: [Table 'mbgoirij_wordpress.wp_3_options' doesn't exist]
    SELECT option_value FROM wp_3_options WHERE option_name = 'siteurl' LIMIT 1

    WordPress database error: [Table 'mbgoirij_wordpress.wp_3_options' doesn't exist]
    SELECT option_value FROM wp_3_options WHERE option_name = 'post_count' LIMIT 1

    Warning: Cannot modify header information - headers already sent by (output started at /home/mbgoirij/public_html/wp-includes/wp-db.php:111) in /home/mbgoirij/public_html/wp-includes/pluggable.php on line 281

    I don't know if this is related to the other problem or not and I'm just now researching this but I thought I would include it in case it offered additional clues to what I've done wrong. What's strange is that in spite of the error message the blog is created and working correctly.

    Thanks again for your help.

    Bob

  7. andrea_r
    Moderator
    Posted 16 years ago #

    The headers already sent usually means whitespace at the end o fthe file. Even on a new upload, some ftp progrmas could be adding it.

    The sql error on manual blog creation has been fixed in trac.
    See http://trac.mu.wordpress.org/browser/trunk/wp-includes/wpmu-functions.php
    to update that file.

  8. alaskanbob
    Member
    Posted 16 years ago #

    Thanks andrea, that solved my sql error. I can now manually add blogs without error.

    I'm still getting the other 'headers already sent error' though. I'm going through the .php files and many of them have a final line like this:
    <?php get_footer(); ?>

    Should I be editing them all so the last line is like

    '<?php get_footer();
    ?>'

    Making sure there are no blank lines after ?> or does it matter that ?> is on a seperate line to end the file?

    Thanks again.

    Bob

  9. alaskanbob
    Member
    Posted 16 years ago #

    I'm at a dead end. I've read all of the related posts. I've checked and double checked for extra characters at the end of the files. All suggestions point to there being a problem with one or both of these files:

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

    But I can't find it. ANY other suggestions? Please.

  10. alaskanbob
    Member
    Posted 16 years ago #

    Is it possible that this is a mod_rewrite problem? Or some other server setting? I know I'm grasping at straws here, but I'm running out of ideas.

  11. andrea_r
    Moderator
    Posted 16 years ago #

    Me too. I dunno, wish I could help you. And I feel your frustration; it's such a stupid error to track down.

  12. alaskanbob
    Member
    Posted 16 years ago #

    ok... getting closer... I think... Now http://allalaskans.com/wp-signup.php link just returns to home page. Any ideas?

  13. Trent
    Member
    Posted 16 years ago #

    After upgrading my database from 3.57.23 all the way up to 4.1.21, I go to wp-signup.php and it just redirects me back to the main page as well. It worked prior to the upgrade.

    I have used the newest version of wp-signup.php in the trac and it didn't fix it. If I go a name that doesn't exist yet, it will let me signup there.

    http://onvertigo.com

    Say if I go to http://onvertigo.com/mu/ it will allow me to take that name.

    Any ideas?

    Trent

  14. Trent
    Member
    Posted 16 years ago #

    Another thing, it works if I go to:

    http://onvertigo.com/wp-signup.php?new=username

    but not:

    http://onvertigo.com/wp-signup.php

    I don't want to change all templates to hardcode the new URL, so does anyone have an idea how to fix this?

    Trent

  15. alaskanbob
    Member
    Posted 16 years ago #

    Thanks Trent. I get the same exact results. So whatever the problem is at least we have duplicated it which gives a better chance of solving the problem.

    Are you using Cpanel to manage your server by any chance?

  16. alaskanbob
    Member
    Posted 16 years ago #

    Ok this is really strange, and now I'm convinced it must have something to do with the rewrite mod.

    go to http://allalaskans.com/ and type anything you want after the / and it will try to create the blog.

    This has to be something simple and obvious but I sure don't know what it is. Also, I'm having trouble with verifying ownership with Google (that 404 reporting 200 error thing) Are the two problems related perhaps?

  17. heyitsaj
    Member
    Posted 15 years ago #

  18. alaskanbob
    Member
    Posted 15 years ago #

    Thank you heyitsay! That was the ticket.

    Bob

  19. MPM
    Member
    Posted 15 years ago #

    "The headers already sent usually means whitespace at the end o fthe file. Even on a new upload, some ftp progrmas could be adding it.

    The sql error on manual blog creation has been fixed in trac.
    See http://trac.mu.wordpress.org/browser/trunk/wp-includes/wpmu-functions.php
    to update that file."

    Is that link/file still up to date?

  20. drmiketemp
    Member
    Posted 15 years ago #

    The link that you give links to the most recent version of that file. When it's an older version, it will have a version number within the URL.

    For example:

    http://trac.mu.wordpress.org/browser/trunk/wp-includes/wpmu-functions.php?rev=1036

    You do see that this thread is many months old though, right?

About this Topic

  • Started 16 years ago by alaskanbob
  • Latest reply from drmiketemp