Support » Theme: Responsive » “Cannot modify header information” error in 2.7

  • Resolved liquidsunshine

    (@liquidsunshine)


    Just started getting this error message since 2.7 update:

    Warning: Cannot modify header information – headers already sent by (output started at /home/username/public_html/wp-content/themes/responsive/core/includes/functions-admin.php:126) in /home/username/public_html/wp-includes/pluggable.php on line 1210

    I was able to fix it by commenting out the <style> section that seems to be incorrectly inserted in the “functions-admin.php” file like so (lines 108-126):

    ?><?php /*
    <style>
    .addon-count {
        display: inline-block;
        z-index: 26;
        margin: 1px 0 0 2px;
        margin-top: 1px;
        margin-left: 5px;
        padding: 0 6px;
        border-radius: 10px;
        color: #fff;
        background-color: #d54e21;
        font-size: 9px;
        font-weight: 600;
        line-height: 17px;
        vertical-align: top;
    }
    </style>
    */?><?php 
Viewing 11 replies - 1 through 11 (of 11 total)
  • fssbob

    (@fssbob)

    I have admin errors everywhere I turn because of the same issue. This appears to be a major problem in the 2.7 update.

    mcolli10

    (@mcolli10)

    I’m getting the exact same issue.

    liquidsunshine

    (@liquidsunshine)

    @fssbob and @mcolli10, does the temporary “fix” I outlined in my post work for you as well? (It might help the developer address the issue more quickly if there’s confirmation of what caused the problem.)

    magenbrot

    (@magenbrot)

    had the same problem, but my functions-admin.php looks somewhat different than yours, @liquidsunshine. I just installed v2.7.1

    In line 108-110 there are tags for ending end beginning a php-codeblock. So at least one blank line would have been printed. After removing them it worked again.

    before:

             * end of each line for what each argument will be.
             */
    ?>
    
    <?php   
            $style = 'display: inline-block;z-index: 26;margin: 1px 0 0 5px;padding: 0 6px;border-radius: 10px; color: #fff;background-color: #d54e21;font-size: 9px;line-height: 17px;vertical-align: top;';
    

    after:

             * end of each line for what each argument will be.
             */
    
            $style = 'display: inline-block;z-index: 26;margin: 1px 0 0 5px;padding: 0 6px;border-radius: 10px; color: #fff;background-color: #d54e21;font-size: 9px;line-height: 17px;vertical-align: top;';
    
    • This reply was modified 1 year ago by  magenbrot.
    liquidsunshine

    (@liquidsunshine)

    @magenbrot – Yep, that’s what I saw when upgrading to 2.7.1 as well. It’s still broken, but removing the extra whitespace still fixes it. It’s a little concerning that two releases in a row have been broken this way… it reduces my faith in the theme devs.

    mcolli10

    (@mcolli10)

    I agree. There is still a blank space between a closing PHP tag and an opening PHP tag at line #109 in version 2.7.1 for functions-admin.php. Those PHP tags don’t even need to be there since the change made from 2.7 to 2.7.1 now assigns the style code block to a PHP variable called $style as outlined by Magenbrot and liquidsunshine above.

    Abigailm

    (@abigailm)

    Same issue here.

    Deleting the blank line 109 from functions-admin.php seems to have fixed it. (If not, I’ll roll back to a previous version until the developer can get things right)

    Theme Author CyberChimps

    (@cyberchimps)

    Hi,

    Sorry for the inconvenience caused.
    This issue has been resolved with the latest version of the theme -version 2.7.2

    Thanks.

    magenbrot

    (@magenbrot)

    Hi @cyberchimps, no problem, thank you for this great theme!

    liquidsunshine

    (@liquidsunshine)

    @cyberchimps — 2.7.2 fixed it, thanks!

    Theme Author CyberChimps

    (@cyberchimps)

    Hi,

    Glad to know that your issues have been resolved.
    Thank you for your patience and understanding.

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘“Cannot modify header information” error in 2.7’ is closed to new replies.