Docs

[Christopher]

Hi there,

I checked and previewed your site with x-child theme and it worked fine, please see the attachments.

Please clear cache and check again.

Thanks.

[totalgeek]

Hello,

I went and looked at the site and it was working as it should be and looked right. However, when I checked my site on GTMetrix I found that the site was still getting knocked for importing the CSS. So I looked at the files in the themes folder and both the old and new child themes are in there. So the site seems to be pulling the CSS from the old child theme still, and not the newer way. I was under the impression when the new child theme was in place that the old child theme would be deleted all together, and the site would only use the new child theme.

I tried to delete the old child theme, leaving only the new child theme in place, and it reverted back to breaking the site again. So I re-uploaded my old child theme I had saved and the site looks normal again. So I’m still missing something here as the site doesn’t seem to work with the new child theme.

Thanks

[Rad]

Hi there,

Do your old and new child theme uses different folder name and theme name? If yes, then make sure that your new child theme has folder name and theme name (you can change that under theme’s style.css).

Switching theme, (activating new theme) will reset some widget and menu settings, or even styling. Because some of it is only specific to the theme or child theme it was applied.

Please also provide a screen recording displaying of how we could reproduce it.

Thanks!

[totalgeek]

Hello,

I’m sorry, I don’t completely understand. The old child theme is named x-child-integrity-light, and the new child theme is named x-child, while the theme itself is named x. I don’t quite understand what you mean about changing the names. I was under the impression I didn’t have to change any names after reading the how-to update post.

I’m a bit confused about the process and don’t exactly understand in terms of the child themes and upgrading. Based on what I had read I thought that I could just update to the new child theme by copying over my existing CSS and functions.php info into the new child theme files, and from there everything would just work as it was working with the old child theme. I had posted on the previous page of this thread the CSS and functions.php file information, for both the old child theme, as well as the new child theme. Both files appear to have almost identical information, minus the @import line in the new CSS/child theme, and the new add_filter( ‘x_enqueue_parent_stylesheet’, ‘__return_true’ ); line in the functions.php file. Could you please review that info I posted and see if there is something amiss there that could be causing the problem.

Again, maybe there is something I’m missing here, but I had thought I could just upgrade to the new child theme, with the CSS and functions.php data listed on the previous page, and the site would look identical without me having to do anything else. Am I mistaken?

Thanks

[Rue Nel]

Hello There,

When we release stacks in X, we use child theme names such as x-child-integrity-light. And then several months after, we release a new child theme which is x-child and this also works when using different stacks. This was made to simplify the child theme. The older ones on the other hand will still works. A few months after we made some changes to the locations of the js and css files. This is why we have release a concrete explanation about it here: https://community.theme.co/forums/topic/child-theme-updates/. As long as you have followed the steps in updating your child theme especially if you are using legacy child theme, your site will be the same.

Hope this helps.

[Rue Nel]

Hello There,

When we release stacks in X, we use child theme names such as x-child-integrity-light. And then several months after, we release a new child theme which is x-child and this also works when using different stacks. This was made to simplify the child theme. The older ones on the other hand will still works. A few months after we made some changes to the locations of the js and css files. This is why we have release a concrete explanation about it here: https://community.theme.co/forums/topic/child-theme-updates/. As long as you have followed the steps in updating your child theme especially if you are using legacy child theme, your site will be the same.

Hope this helps.

[totalgeek]

Thanks for the information, it sounds like I should be able to switch over to using the new child theme, without losing anything in terms of how the site looks or functions today. Which is what I had originally thought when I read https://community.theme.co/forums/topic/child-theme-updates/. I thought I just had to add the new child theme, swap over my CSS and functions.php, and then I would be all good.

Clearly though I must be missing something, as I think I’ve done the steps as listed in the how-to thread, and it’s not working. As soon as I get rid of my old child theme, and replace it with the new child theme, it breaks the site. I reviewed the CSS file contents, as well as PHP file contents of both the new and old child themes, and I posted that content on page 2 of this thread, could someone look at that content between the files and make sure it looks correct? Based on everything I’ve read, the content of the CSS and PHP file for the new child theme have exactly what they need to in order to have the site look identical to how it does with the old child theme, but it doesn’t work when I use the new child theme.

The only way the site will function and look as it does currently, is if I leave the old child theme with the @import statement in place, but I want to update as per the how-to to avoid every running into this issue again. I appreciate the help in trying to figure out why it’s not working.

Thanks

[Rue Nel]

Hello There,

There is nothing wrong if you are still using the old child theme. As long as you have updated this line, your site will display fine.

@import url( '../x/framework/css/dist/site/stacks/integrity-light.css' );

Now if you want to switch to the new one, you can also do that however, please do not switch right away. You must backup your customizer settings. You need to download the XCS file. Once you have a backed up then that’s the time you can switch to the new child theme. Right after activating the new child theme, you need to import the XCS file to make sure that you will have the previous setting. For further details, please check it here: https://community.theme.co/kb/customizer-manager/

Hope this helps.

[Author]

Posts