Syahir Hakim

Keymaster

Forum Replies Created

  • Admin

    In reply to: [BETA] Graphene 1.3b

    #14184

    OK, I’ve fixed the other two bugs you mentioned.

    I think I’ve figured out the problem with the images, but I’m not sure if I can fix it on my end. In the style.css file in version 1.3b, I’ve added a new property width: auto; to the .entry-content img selector:

    .entry-content img,
    .wp-caption {
    max-width: 98%;
    width: auto;
    height: auto;
    }

    It wasn’t there before, but it’s required in order for Internet Explorer (can’t remember whether it’s IE7 or IE8) to resize the image automatically if it exceeds the content area.

    But still, I think the real problem is that WordPress isn’t resizing the images that you uploaded to the server. This could be due to permission problems, or the necessary image manipulation module or extension is not installed/enabled in your server.

    When you remove the width: auto; from the CSS, the image shows up in the size you wanted it to, but just because the HTML element for the image has the height and width attribute assigned to it. This means that the browser still have to download the full-sized images (1024×768), and then resize it down to the thumbnail size (200×150). This is of course a waste of bandwidth, and cause the images to be loaded slowly by the browser because the file size of the full-size images are quite large (300+ KB).

    Admin

    In reply to: [BETA] Graphene 1.3b

    #14181

    Hurm..I just downloaded one wallpaper to my comp, uploaded it to my test install, and inserted it into a post at 225×300 pixels, and it shows up at exactly that size. It might be that WordPress failed to resize the photos when uploaded to your server. Try check the permissions on the wp-content/uploads/ folder?

    Admin

    In reply to: [BETA] Graphene 1.3b

    #14179

    Hurm..I don’t think this i caused by the theme..it doesn’t modify the full post content in any way. Can you try adding just one of those images again with the size that you wanted?

    Admin

    In reply to: How to change post title size

    #13765

    Remove the second set of /* and */ from your code, so that it becomes like this:

    /*
    Theme Name: graphene-child
    Theme URI: http: //www.rudragems.com/
    Description: Child theme for the Graphene theme
    Author: Vaibhav Bathla
    Author URI: http: //www.rudragems.com/about/
    Template: graphene
    Version: 1.0
    */
    @import url("../graphene/style.css");
    h2, h2 a, h2 a:visited {
    font-family: georgia,verdana,tahoma,arial;
    font-size: 25px;
    padding-bottom: 4px;
    }

    Adding those will cause the content in between them to be commented out, and ignored by the browser.

    Admin

    In reply to: [BETA] Graphene 1.3b

    #14177

    Hurm..do you have the website online or you’re testing it locally? I can’t seem to reproduce the bug you’re describing.

    Admin

    In reply to: [BETA] Graphene 1.3b

    #14175

    Hi Tigeryoshi,

    Can you describe the bug in a little but more detail? E.g. how to reproduce the bug you’re seeing.

    Thanks!

    Admin

    Looks like you copied over the whole content of the theme’s style.css into the child theme’s style.css file when you made the child theme, which you should not do. Please re-read the instructions I posted here: https://forum.graphene-theme.com/topic/how-to-modify-the-theme-using-a-child-theme

    Admin

    In reply to: Problem with video

    #14122

    Topic moved from General Talk to Support. Please post in the correct section next time.

    Admin

    In reply to: Hide post tags – will the search engins index them?

    #13745

    This CSS will do:

    .post-tags{
    display: none;
    }

    Keep in mind though that it ultimately depends on the search engine’s algorithm whether or not it will take the hidden elements into account or not. Or you could also probably try something like this:

    .post-tags{
    position: absolute;
    left: -999em;
    }
    Admin

    In reply to: Problem with child pages' thumbnails

    #14207

    Hi NeoEGM,

    Yes, this is a known issue and has been fixed in the upcoming version 1.3. Hopefully, if everything goes right, it should be available to the public in the next few days.

    Thanks!

Viewing 10 posts - 4,981 through 4,990 (of 6,030 total)