Hi @aglea
Great question. It actually depends on the child theme.
When you use a Storefront child theme, updates you make in Storefront Powerpack should be applied as well, but only if the child theme is coded to allow that. Some child themes may not be coded that way and may still override the changes you’ve made in Powerpack.
If that’s not the case for you (and you don’t see the changes you make in Powerpack), it’s best to reach out to the developer of the child theme; they should be able to help you with that .
Thread Starter
Aglea
(@aglea)
Hi Senff, Thank you for the reply.
So it appears the Powerpack customizations take precedent over the Child Theme, which I wasn’t expecting. So I guess Powerpack was designed not to be used with a Child Theme.
However, I’m thinking — and let me know if it’s overkill — that I will keep the Child theme anyway. I’m thinking in future (if I can ever get the hang of this), I might want to copy in page templates to edit, and as I understand it, the correct way to do this is to copy them into the child theme folder from Storefront, so they don’t get overwritten on updates. Ditto with functions file.
I still don’t see anywhere where the Powerpack setting are kept and it’s nice to see changes in real time and definitely easier than making changes on the child theme.
So I guess I’ll use both PowerPack and Child theme with storefront.
Thanks for your help!
So it appears the Powerpack customizations take precedent over the Child Theme, which I wasn’t expecting. So I guess Powerpack was designed not to be used with a Child Theme.
Powerpack has been designed to override all styles you use, regardless of the theme (so it doesn’t make a difference whether that is a parent theme or a child theme).
You can code your child theme in such a way that Powerpack settings will not be able to overwrite your child theme styles (using !important in your CSS declarations), but then there would be no point anymore using Storefront. 🙂