Header image size problems…?

  • Luko

    #2576

    Hy,

    I changed header image size like Syahir described here:

    https://forum.graphene-theme.com/graphene-support/header-image-size-change#post-345

    Working fine on localhost, but when I put it in the server, after some time I get white screen of death (WSOD), when loging in, publishing posts, making new category et.

    Then I disabled ALL plugins and the problem persisted.

    With Wp-debug checked, get the error in functions.php of child theme?(line 1., refferd by pluggable.php, in this line:

    header("Location: $location", true, $status);)

    In child functions.php only have this:

    <?php
    function graphene_custom_header_width(){
    return 960;
    }
    function graphene_custom_header_height(){
    return 120;
    }
    add_filter('graphene_header_image_width', 'graphene_custom_header_width');
    add_filter('graphene_header_image_height', 'graphene_custom_header_height');
    ?>

    Now, I deleted entire file (functions.php) in child theme, working fine now.WTF?

    No WSOD, site looking same, only now plugin “Category posts widget” won’t work.

    This plugin problem is NOT the issue. I’m just asking is it normal that new header size working without that code in functions.php???

    Is this theme issue, or WP, or Host Provider, or (that’s most likely) I screwed up something. 🙁

    http://kuglanje.net

    P.S.

    Only have this plugins:

    -Akismet (not activated)

    -Dropdown menu widget

    -Cagtegory posts widget (not working – deleted)

    getting error in cat-post.php in this line:

    ‘$cat_posts->the_post();’

    Sorry for messed up post.I’m in a hurry!!!

    Josh

    #20967

    The header is keeping your new display size because you already adjusted the size using CSS… the #header property.

    The functions Syahir provided, are meant to help with the auto-cropping graphene does with the normal header image behavior.

    When you remove this function, it just means next time you auto-upload a new header, it will be cropped as normal.

    Luko

    #20968

    Great,

    so it can run like this until I wish to put another header.

    If I put another header manually (not from admin dashboard) will it work without functions.php?

    Well I C for myself, if not, i know what is the problem. 🙂

    Thanks Josh for explanation.

    Any ideas for WSOD issue?

    BTW, your plugin works great, will donate.

    Josh

    #20969

    Aw, thank you 🙂

    Yeah, it will stay the same. You can always use FTP or cpanel to “replace” the default header image with a new one and it will keep your dimensions. You have to make sure to keep the same name though, and OVERWRITE the one being used now.

    But if you upload through admin, it will be cropped.

    WSOD usually happens when there is a conflict in the code. It’s nice when you get a “warning” or a “fatal error”, because it can point you in the right direction of how to fix the problem. However, with a WSOD, it’s almost impossible to identify a specific cause.

    You’re doing great if you have traced it to a specific plugin, most people have NO idea where it originated from, must deactivate ALL plugins, and start afresh.

    Can you post the entire error being generated?

    Luko

    #20970

    Warning: Cannot modify header information – headers already sent by (output started at /home/kuglanje/public_html/wp-content/themes/graphene-child/functions.php:1) in /home/kuglanje/public_html/wp-includes/pluggable.php on line 754

    It happens only if functions.php (with Syhir code only in it) is in child-theme folder.

    Josh

    #20971

    Check the white space in your child theme functions.php. You should have NO extra space or lines before the opening <?php and the closing ?>.

    This warning is usually generated when you have erroneous white space in your php files.

    For instance, the <?php can’t begin on line 2. And the closing ?> can’t have any extra lines after it.

    Luko

    #20972

    Checked that first, no extra space before and after. Opend it with Dreamweaver and in the line 1. stands just open php tag (<?php), also the last line in functions.php is closing tag (?>).

    First appearance was white screen only, then I enabled WP_DEBUG in wp-config.php ‘(define(‘WP_DEBUG’, true);’, and above statement pop out.

    It’s OK now, without functions.php in child-theme!

    Thanks for assist.

    Mod

    Kenneth John Odle

    #20973

    Most text editors have a command like “trim trailing space” which will remove all spaces, tabs, and returns at the ends of lines. This is a very useful feature. I use Notepad++, which does this nicely.

Viewing 8 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic.