WordPress.org

Support

Support » Themes and Templates » Hey Cookie » [Theme: Hey Cookie] css for ie being brought in for Firefox, Safari, and Chrome.

[Theme: Hey Cookie] css for ie being brought in for Firefox, Safari, and Chrome.

Viewing 10 replies - 1 through 10 (of 10 total)
  • WPyogi

    @wpyogi

    Forum Moderator

    If you post a link to your site, someone can probably help you with this.

    To clarify, I am using Caorline’s own demo site to point out what seems to be an error in ie.css handling.

    http://heycookie-demo.calobeedoodles.com/

    A second call is being made to ie.css that is not suppressed in other browsers, and because it comes in last minute, it overrides default style.css in those other browsers.

    This Firefox snapshot shows how the header h1.title has a 28px attribute which is *only* an ie.css attribute.

    https://skitch.com/fishback/82rbn/hey-cookie-ie-css-example

    Theme Author Caroline Moore

    @sixhours

    I don’t have ready access to my computer at the moment, but I’m pretty sure this is temporarily intentional behavior while I work on making the theme responsive. I could be wrong, tho. I started a new job this week and am currently traveling/training, so probably won’t have time to delve into this theme for awhile, but I’ll make a note of this for the next time I do. Thanks!

    I dug a little further. It seems to be that the conflicting ie style call is being brought in at the end of the header by:

    <?php wp_head(); ?>

    Will dig further. Congrats on new job! I’m experimenting with Hey Cookie over here… GraphicJoke.com

    Theme Author Caroline Moore

    @sixhours

    Yes, check functions.php for the style registrations. 🙂

    Looks like functions.php. There is an “if” statement commented out and then by default ie.css is being brought in, even with no-ie browsers. So ie is overriding default style.css with non-ie browsers as well as overrides my own theme options css since those come in prior to this call.

    /*if( isset( $hey_cookie_responsive ) && $hey_cookie_responsive == 1 ) {
    wp_register_style( ‘hcmedia’, get_template_directory_uri() . ‘/media.css’ );
    wp_enqueue_style( ‘hcmedia’ );
    }
    else {*/
    wp_register_style( ‘hcmediaie’, get_template_directory_uri() . ‘/ie.css’ );
    wp_enqueue_style( ‘hcmediaie’ );
    //}

    I gather you are preparing for a responsive option in theme options (not showing yet) and for now are, in effect, defaulting to style inside ie.css. Well at least I know where to customize (since this all happens after the Custom CSS field statements.) I’m good for now!

    PS.
    The PayPal button at the bottom of theme options didn’t go anywhere for me.

    <form action=”https://www.paypal.com/cgi-bin/webscr” method=”post”>

    Will go PayPal the manual route!

    [ Moderator Note: Please post code or markup snippets between backticks or use the code button. ]

    Just upgraded to Hey Cookie 1.2.9 and the ie.css problem is still there. In functions.php because the if statement is commented out, in all cases the /ie.css is registered. This is creating conflicts in look with non-IE browsers as well as conflicts with the user custom CSS field since /ie.css is pulled in after the custom css is displayed in the header.

    /*if( isset( $hey_cookie_responsive ) && $hey_cookie_responsive == 1 ) {
    		wp_register_style( 'hcmedia', get_template_directory_uri() . '/media.css' );
    		wp_enqueue_style( 'hcmedia' );
    	}
    else {*/
    		wp_register_style( 'hcmediaie', get_template_directory_uri() . '/ie.css' );
    		wp_enqueue_style( 'hcmediaie' );
    	//}

    Theme Author Caroline Moore

    @sixhours

    Yep, I haven’t had a chance to look at this yet… I’m swamped. When it’s fixed, I’ll make sure to note it in the readme.

    In the meantime, you can probably revert to an older version of the theme using the SVN repo… the old, pre-meddled-with functions.php and stylesheets are there.

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘[Theme: Hey Cookie] css for ie being brought in for Firefox, Safari, and Chrome.’ is closed to new replies.
Skip to toolbar