[kjdennyParticipant]

Unfortunately, the instructions supplied by Themeco staff to implement a child theme simply do not work. I have been trying to get an answer for a day now, without success.

Since the last update installed, the child theme does not work.

I have installed the latest child theme, as per instructions. However, none of the styles entered on the style.css file in the child theme apply. None. The ONLY way I can make any style changes is to go into Customizer and enter the style code in the “Custom” field. This is not satisfactory when one is making extensive customizations.

Because I make a lot of changes to the theme, I want to use the child theme structure. Sadly, I cannot because of whatever bug is in place now. Of course, there may be some crucial instruction/step required that you have not explained, but I am at a loss to find it. I gave my login details, on my topic post, but that doesn’t seem to have helped.

In the past, I was very pleased with the theme, and intended to use it again and purchase more licenses, but this problem, along with ALL the glitches with Cornerstone, I will not.

[kjdennyParticipant]

Unfortunately, the instructions supplied by Themeco staff to implement a child theme simply do not work. I have been trying to get an answer for a day now, without success.

Since the last update installed, the child theme does not work.

I have installed the latest child theme, as per instructions. However, none of the styles entered on the style.css file in the child theme apply. None. The ONLY way I can make any style changes is to go into Customizer and enter the style code in the “Custom” field. This is not satisfactory when one is making extensive customizations.

Because I make a lot of changes to the theme, I want to use the child theme structure. Sadly, I cannot because of whatever bug is in place now. Of course, there may be some crucial instruction/step required that you have not explained, but I am at a loss to find it. I gave my login details, on my topic post, but that doesn’t seem to have helped.

In the past, I was very pleased with the theme, and intended to use it again and purchase more licenses, but this problem, along with ALL the glitches with Cornerstone, I will not.

[Rue NelModerator]

Hello There,

Sorry for the confusion. I would apologize for not being straight forward in giving the solution to your issue in our previous reply. We haven’t give you much explanation on how styles were being loaded. Please keep in mind that any styles in a parent theme is the default global styles for the theme. Your custom styles in the child theme overrides the default global styling in the parent theme. The customizer on the other hand is a place for you to easily change the colors, background colors, border colors, font size, font family, etc which would override the default settings you have in the parent or the child theme.

To explain you better about how the styles were loaded in X and how the customizer overrides any of the styles both in the parent and the child theme, the styles were loaded on the page in this order;
– Parent theme’s style.css
– Child Theme’s style.css
– Customizer’s custom css
– Cornerstone’s Custom css in the settings tab

With this order, this would explain why the customizer works and the child theme does not. I have checked your child theme’s style.css and you have this code:

.x-btn, .button, [type="submit"] {
   border-top:none;
   border-right:1px solid #363896;
   border-bottom:4px solid #363896;
   background-color: #eaeaea;
}

This would not work out and will always be overwritten with the customizer settings for your buttons. To make sure that the child theme’s style.css will not be overridden by any css, you must use a specific selector like this:

.x-child-theme-active .x-btn, 
.x-child-theme-active .button, 
.x-child-theme-active input[type="submit"] {
   border-top:none;
   border-right:1px solid #363896;
   border-bottom:4px solid #363896;
   background-color: #eaeaea;
}

Hope this helps.

[kjdennyParticipant]

Before I give up totally, I would be really, really grateful if someone could look at my websites, as per the logins sent earlier in this strand and explain to me why child themes simply do not work with my installations.

As I have said before, I have followed every instruction, have the latest version of the child theme installed, but it simply does not work.

If the child theme is faulty and doesn’t work, then just tell me so. If there is some step I haven’t taken, that needs to be done to make it work, then I’d really appreciate knowing what it is.

Thank you.

[kjdennyParticipant]

Sorry – didn’t see that you had replied. It isn’t just the buttons being overwritten, it is everything – none of the changes I have written apply. It seems to be that the only solution is just to load all the customization into the Custom field in Customizer. Which is the work-round I have used in the past and will have to use again, though it is hardly ideal. By the way, Cornerstone also has a conflict with Gravity Forms (pretty serious) see attached screenshot. It is definitely your theme, because when I disable all plugins, and load another stock theme, the conflict disappears. When I activate X child theme, bingo – the conflict is back again. Gravity forms say they have had other people in touch with them about this same problem. It affects both confirmations and notifications and prevents editing them. There is a clunky work-round (load and activate stock theme like twenty fourteen, make necessary changes in notifications and settings, then reactive x child – a pain, to say the least….)

[Rue NelModerator]

Hello There,

It seems that you have a custom code in your child theme’s functions.php file. I would recommend that you remove it first or at least update the code. By default the child theme works out with the parent theme. As soon as the user overrides the stylesheet or how the styles will be loaded by using a custom function in the child theme will likely to result an issue. This is the case in your child theme. It took us several replies from us defending and trying to figure out the issue. The problem was your custom function that you have added. If you please try to remove it and test your again, this may resolve this issue.

Please let us know then. Thank you very much for your understanding.

[kjdennyParticipant]

Placed that code copied and pasted from one of your forum strands from staff when I was trying to sort the child theme problem myself. Have removed now, and it has done the trick.

Just so I am really clear as the child theme issue, if it is a style that is defined through customizer normally – eg buttons, text size etc – that will always take precedence over code placed in the child theme css. So, in theory, custom css relating to say Gravity forms styling, SHOULD work if placed in the child theme style css file. Is that correct? child theme css should be used for styles and elements not defined within Customizer.

[kjdennyParticipant]

Have just tried that and it doesn’t seem to work. Could you give me some guidance as to which elements – if any – are best handled by placing the code in the style.css file of the child theme?

Sorry to be thick, but I am really trying to get my head around this. If the customizer’s custom css field is empty, and there are no style added via cornerstone, then shouldn’t the child theme css take precedence?

[FriechModerator]

Hi There,

Not really, there are three types of CSS styles:

Inline styles, inline styles are styles that are written directly in the tag on the document.

e.g.
<p style="color:blue;">Lorem Ipsum Dolor</p>
<h2 style="font-size:50px;">Lorem Ipsum Dolor</h2>

Embedded styles, embedded styles are styles that are embedded in the head of the document (<head> of the page).

e.g.
The Custom CSS that you wrote on the Customizer and Cornerstone settings custom css.

External styles, written on a external files.

e.g.
The Style.css file of the parent and child theme, the style.css file of gravity forms and other plugins.

In terms of conflict; the basic rule is Inline styles over the other two. Embedded styles over External styles.

The tricky part, in terms of conflict with the same type. For example the CSS file relating to Gravity forms and child theme’s style.css. The rule is whichever the styling that has the higher specificity will take effect.

Please follow this link how to determine CSS Specificity.

Also keep in mind that there are css styles that declared as !important (not recommended), this declaration will ignore everything and over rule all the conflicts.

e.g.

.myclass {
background-color: red !important;
}

Would you mind to clarify to us which of your style.css on child theme that did not work? And provide us the site URL as well so we can take a closer look.

Hope this shed some lights.

Cheers!

[kjdennyParticipant]

Hello,

Have narrowed it down specifically to the css relating to the bar that appears over the links in the navigation menu.

This is the code I want:

.x-navbar .desktop .x-nav > li > a:hover, .x-navbar .desktop .x-nav > .x-active > a, .x-navbar .desktop .x-nav > .current-menu-item > a {
box-shadow: 2px 0 0 0 #363b96 inset;
}

When placed in style.css it does not work; when placed in Custom/Customizer, it does. I assume that means there is a setting, somewhere else in Customizer that takes precedence over style.css; however, under heading there is the option to change the colour of the navigation links text and hover, but not to edit the appearance of that bar.

[ChristopherModerator]

Hi there,

Please update your code in child theme’s style.css file to :

.x-navbar .desktop .x-nav > li > a:hover, .x-navbar .desktop .x-nav > .x-active > a, .x-navbar .desktop .x-nav > .current-menu-item > a {
    box-shadow: 1px 0 0 0 #1b1d96 inset !important;
}

Hope that helps.

[kjdennyParticipant]

Thank you.

[ChristopherModerator]

You’re welcome.

[Author]

Posts