Forum Replies Created

  • In reply to: Compatible with Internet Explorer



    Don’t know if this has already been discovered, but if not, I’ve figured out the reason to the problem I posted.

    I may just be repeating what someone else has already said, and I just haven’t been able to find it in the forums, so apologies for that.

    The reason my colour changes were taking in Safari and Firefox and Chrome but not IE or Opera was because those last two browsers don’t seem to support any of the various gradient commands. This is obviously already known, for this is the reason for the “bg-sidebar-h3.png” and like files, which is effectively a hard copy of the gradient. It’s this file that IE and Opera uses (and Safari for iPhone as it turns out). Because I hadn’t changed the path to the image in my child style.css, the colour used was the single shade defined at the end of that first “background…” line.

    Thus, to fix it, I opened the png files in Photoshop (there’s one for the widget headers and two for the block buttons), used my specified colour values to fill the png’s with my new gradient, saved them to my child folder and changed the paths in the css file accordingly.

    It seems to have done the job.

    P.S. If you have a Mac and want to know how your site looks in IE, use “IE NetRenderer”, it’s a website and supplies you with a simple screenshot of your site in any IE version of your choice.

    In reply to: Compatible with Internet Explorer



    I too am having grave Internet Explorer problems. I thought everything was great until I viewed my site at work using IE8 on a Windows machine.

    My site is

    Here is what it looks like in Safari and Firefox: site_good.jpg

    Here is what it looked like in IE8: site_bad.jpg

    From reading this thread I checked out the source, and nothing looks untoward to my untrained eyes except for the bit in the <head> that looks like this:

    <!--[if lte IE 8]>
    <style type="text/css" media="screen">

    I’ve also included some portions of my child style.css which relate to the elements in question:

    .sidebar h3 {
    background: url(images/bg-sidebar-h3.png) left bottom repeat-x #3C9CD2;
    background: -moz-linear-gradient(#BB5822, #401A05);
    background: -webkit-linear-gradient(#BB5822, #401A05);
    background: linear-gradient(#BB5822, #401A05);
    border-bottom: 1px solid #040D17;
    -moz-border-radius: 5px 5px 0 0;
    -webkit-border-radius: 5px 5px 0 0;
    border-radius: 5px 5px 0 0;
    color: #fff;
    *display: inline;
    font: bold 16px/20px arial;
    margin: -15px 0 5px -12px;
    padding: 7px 12px;
    text-shadow: 0 -1px 0 #555;
    width: 100%;
    zoom: 1;
    .home #content {
    background: -moz-linear-gradient(#4B4D5D, #171C41) repeat scroll 0 0 transparent;
    padding-bottom: 0px;
    padding-top: 21px;
    #content {
    background: -moz-linear-gradient(#4b4d5d, #171c41);
    background: -webkit-linear-gradient(#4b4d5d, #171c41);
    background: linear-gradient(#4b4d5d, #171c41);
    padding-top: 21px;
    padding-bottom: 20px;
    .sidebar div.sidebar-wrap {
    background: #fff;
    border: 1px solid #45496b;
    -moz-box-shadow: 0 0 5px #BBB;
    -webkit-box-shadow: 0 0 5px #BBB;
    box-shadow: 0 0 5px #BBB;
    margin-bottom: 16px;
    padding: 10px 12px;
    position: relative;
    #sidebar_bottom {
    background: #171c41;
    clear: both;
    margin-top: -10px;
    padding: 0 0 20px 0;
    #sidebar_bottom .sidebar-wrap {
    display: inline-block;
    margin: 10px 1px 5px 14px;
    padding: 10px;
    vertical-align: top;

    Any help, as always, much appreciated.


    Thanks for the code Syahir.

    It does work, however I then noticed that you’ll get two instances of the social sharing buttons on a single-post page. LOL.

    I haven’t tried it, but I would assume this is easily worked around by doing something like this:

    function graphene_custom_addthis_placement(){
    if ( is_single_post() ) :
    else :
    graphene_addthis( get_the_ID() );
    add_action( 'graphene_after_post_content', 'graphene_custom_addthis_placement' );

    However, I still couldn’t get the buttons above my other end-of-post plugin. In the end, I did it all manually in my child’s functions.php. Fortunately my other end-of-post plugin has an option to use code, and then because I disagree with AddThis forcing a “via @addthis” string to the Tweet button, I did the buttons myself, too.

    For those that may want to do something like that, here’s the code I ended up doing (I’m a beginner, so apologies to you demon-coders who could do this with half the lines 🙂

    function my_buttons(){
    if (is_page()) :
    else : ?>
    <script src="" type="text/javascript"></script>
    <a href="" class="twitter-share-button"
    data-url="<?php the_permalink(); ?>"
    data-text="<?php the_title(); ?>"
    <g:plusone href="<?php the_permalink(); ?>" size="medium"></g:plusone>
    <script type="text/javascript">
    (function() {
    var po = document.createElement('script'); po.type = 'text/javascript'; po.async = true;
    po.src = '';
    var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(po, s);
    </script><br><h3>You may also like...</h3>
    <?php get_related_posts_thumbnails();
    add_action( 'graphene_after_post_content', 'my_buttons' );

    So here I’ve got a Tweet button for the specific post, and G+1 button that does the same. Then after the two buttons I put in a line break before calling the other plugin (a related posts plugin).

    Doing it this way allows me to control the order of the plugins, and also do little things like adding an empty line between the end of the post and the sharing buttons.

    You can see how it looks here.

    Hope this has been helpful to someone 🙂

    In reply to: How to modify the theme using a child theme


    I have what might be a really dumb question. I’m now using a child theme (woo-hoo), but had previously modified loop.php. I’ve now copied loop.php to my child-theme directory, so that when the next update arrives my changes won’t be lost.

    My dumb question is this: when you release new updates of the theme, do the .php files never change? For example, if your update includes a change to the loop.php, surely I’m not going to see that change because I’m using my own loop.php in my child-theme directory.

    Clarification appreciated and, as always, thanks for such a great theme.

    In reply to: Thanks, colours and widgets


    Hi, Syahir, and thank you for your continued support.

    If I add the #, it disappears as soon as I leave that field, and I’ve already tried using the colour picker. I presume that the widget, slider and button previews are supposed to change when you pick the colours, but they don’t, they remain blue.

    Basically, my “Colour Options” just doesn’t work. You obviously haven’t come across this before, so I would assume it’s a conflict with a plugin that I’ve installed. Does this sound logical?

    I have quite a few, so do you recommend any way I could find out what’s causing the conflict without deactivating each plugin, as that will obviously delete all settings associated with that plugin?

    Thanks again.

    In reply to: Thanks, colours and widgets


    Hi Syahir,

    Thanks for your reply. I know about the # needed when using CSS, but I was using the “Colours Options” panel. I can change any colour, either by keying in the number or using the colour picker provided, but while the changes are saved in the options, they don’t change on my website.



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

Graphene Themes Forum