- This topic has 5 replies, 2 voices, and was last updated 1 month, 1 week ago by Leo.
August 14, 2020 at 4:21 pm #1403383Randy
When changing Theme from plain GeneratePress to a GP child, the site “often” or “usually” loses the header image (customizer-> site identity-> logo) and/or custom text in the footer (customizer-> layout-> footer-> copyright). Which is to say, after such a change there’s no graphic in the header, and the copyright goes back to default. Seems to me that nothing “should” be lost in such a transition, at least when it’s a GP-to-GP transition. It’s pretty consistent when I’ve had to build a new Child because a site has gone from “simple” to “more complex.” When I’m done and make the theme switch, those elements are gone.
It has happened to me several times on several different sites without theme changes, too. It’s your “favorite” kind: non-reproducible intermittent. I’ll just pop over to a site to do something, and will notice the header image is gone and footer is default. I have no idea what triggers it, but I have to stop what I was doing and fix that. Our sites need the branding to stay once it’s set….
Thanks!August 14, 2020 at 5:56 pm #1403422LeoStaffCustomer Support
Does happen to an empty child theme from here?
I’ve never heard this before and it sounds some sort of caching issue.August 14, 2020 at 8:27 pm #1403492Randy
I hand-coded my first GP child theme, and then copy over the parts I need when adding it to another site. Which is to say I unix cp to the new location, chown it, check what I need it to do, and then go into the WP back end and do the switch there.
Usually a site where I do this doesn’t have any caching plugins at that point, since it’s going into a low-traffic site (where traffic is increasing, or expected to).
The fix is easy enough: go into the customizer and re-setting the icon and footer text. That’s not too terrible when I’m in there working anyway (such as switching to a child theme), but the occasional loss of those two elements without “notice” is still an issue, as it’s there unbranded until I happen to look at the front end and go “uh oh!” (And then I fix it in the customizer.)August 14, 2020 at 9:09 pm #1403509LeoStaffCustomer Support
If you can somehow test it with an empty child theme I linked then that would be great!
We have not received any other reports on this so not sure if there’s anything we can fix here.
A child theme is pretty simple – it just grabs everything from the parent theme (including the customizer settings) with two extra files for CSS and functions.August 14, 2020 at 10:02 pm #1403557Randy
Yep, I know it’s very simple, at least from the start. 🙂
Part of my idea in posting is in hopes if other affected users have seen this, they’ll pop in with “Me toos” (and hopefully more info that helps define the issue).
Or maybe even Tom will say “Hm, I think I know what that might be…” and poke around.August 15, 2020 at 8:10 am #1404118
- You must be logged in to reply to this topic.