Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #18240

    Hi

    I have made .php edits along the way and as I was now looking to update the theme to v.1.7 from v.1.6, I thought it would be a good time to start doing things correctly and make a child theme.

    When I put in the simplest of starting points (see below) it reverts the site almost back to the starting point of a new installation. No background, extra menu items, page’s no longer showing portfolio items etc.

    What would you recommend I do now, or is it easier to continue without a child theme?

    thank you

    Tim

    /* Theme Name: Child of Propulsion

    Description: Child Theme by Tim Rowley for Propulsion Theme by Kriesi

    Author: Kriesi

    Template: propulsion */

    @import url(“../propulsion/style.css”);

    #98718

    Hi,

    Are you using your custom.css file in the parent theme? If you are then you need to copy its contents and add them to the bottom of style.css in the child theme.

    Besides that, all else should remain identical. I just tested a child theme with Propulsion locally and was able to switch between the parent and the child without losing any settings.

    Please try your style.css like this

    /*
    Theme Name: Child of Propulsion
    Description: Child Theme by Tim Rowley for Propulsion Theme by Kriesi
    Author: Kriesi
    Template: propulsion
    */
    @import url("../propulsion/style.css");

    Propulsion Child-Theme Download

    Thanks,

    Nick

    #98719

    Hi

    trying to make a child theme also.

    I’ve added my CSS in my style.css file after the @import url(“../Propulsion/style.css”);, but none of my redefines of existing Propulsion styles work because my CSS is in fact overridden by Propulsion CSS!

    That’s because Propulsion’s style.css is actually empty and all style sheets are loaded manually in the header.php:

    <!– add css stylesheets –>

    <link rel=”stylesheet” type=”text/css” media=”all” href=”<?php bloginfo( ‘stylesheet_url’ ); ?>” />

    <link rel=”stylesheet” href=”<?php echo get_bloginfo(‘template_url’); ?>/css/grid.css” type=”text/css” media=”screen”/>

    <link rel=”stylesheet” href=”<?php echo get_bloginfo(‘template_url’); ?>/css/base.css” type=”text/css” media=”screen”/>

    <link rel=”stylesheet” href=”<?php echo get_bloginfo(‘template_url’); ?>/css/layout.css” type=”text/css” media=”screen”/>

    <link rel=”stylesheet” href=”<?php echo get_bloginfo(‘template_url’); ?>/css/slideshow.css” type=”text/css” media=”screen”/>

    <link rel=”stylesheet” href=”<?php echo get_bloginfo(‘template_url’); ?>/css/shortcodes.css” type=”text/css” media=”screen”/>

    Doesn’t that go against the working principles of the WordPress styling mechanism? How am I supposed to work around that?

    Add a custom action on wp_head to insert a <link> to my style sheet there?

    Thanks

    #98720

    Hi there, I managed to create a propulsion child theme using Nicks really helpful instructions in this thread.

    http://www.kriesi.at/support/topic/what-do-i-need-in-my-child-theme-functionsphp-file-for-it-to-work-properly#post-81543

    Once installed, I needed to go through the basic settings again to put in place the colour and text styles,widgets etc. I had created using Propulsion. But once that was done it all worked perfectly except for one thing which I’m hoping you can help me with.

    On the product detail pages, I had chosen not to use the featured media box to insert images. Instead I inserted the image straight into the main content box. I did this to create a particular page layout that I couldn’t achieve with the featured image box.

    However with the child theme in place, the products now appear in the featured image box style by default. So If I go in to edit the page, the image is appearing automatically in the featured image box. Other than going through each individual product page, removing the image from the featured image box (250 products so will take a while) is there a way of achieving this globally?

    Susan

    #98721

    Hi Susan,

    Thanks for posting the link to my post on child themes, I was looking all over for it because I rather not retype it again.

    That is a really weird problem. You mean you just add the html IMG tag into the main content area and when you save the page it disappears from the content but re-appears in the featured image?

    If that is what you meant, I can’t replicate this event.

    There is some reason why the stylesheets and scripts are not en-queued. Something to do with the dynamic template being on same page with ajax portfolio I think. However you have zero chance of duplicating those files since they are all proprietary to the theme. I will double check.

    Thanks,

    Nick

    #98722

    Hi Nick, it is a little different from what you outline above. Basically in propulsion the image is inserted into the content box and text added.

    Nothing is put into the featured image box.

    On reversion to the child theme, the content box still has the image and text. But additionally, the image appears in the featured image box. On the live page, you then have two version of the image. One in the left sidebar which comes from the featured image box and one filling the main page content box which is the the correct one.

    Susan

    #98723

    Hi,

    I just tested and the only thing I noticed was that if you had a featured image set in the parent theme, it is not shown in the child theme. But I didn’t experience what you describe. I have a suspicion though, if it happens, it only happens if in the past you had some kind of featured image set for that product and then removed it.

    Can you repeat what i’ve done in the screen-cast ( https://docs.google.com/open?id=0B8hqGBMSfHtKNWdFam5SVXBIWFU ) (a) create new product in parent theme (b) add image to the content (c) switch to child theme to look at page. Will you have the same results or are they different.

    I will do more testing and notify Kriesi. My suggestion is to either (a) return to using parent theme (b) enter 200 products all over into child theme (c) mask the duplicate image using css in the child theme. I would go with C, since can hide the image easily and there is no disadvantage in load time since both images are identical.

    #top.single-product .slideshow_container {
    display: none;
    }

    See if that does the trick.

    Thanks,

    Nick

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

The topic ‘Creating a Child of Propulsion’ is closed to new replies.