You cannot have a beneficial parent-child relationship unless you create a child theme from the start. Cloning an entire theme and calling it a child theme will offer zero benefit. Themes are updated manually but unlike machines, people have been known to make mistakes and accidentally update customised themes. At that point, there is nothing we can to to help them.
So, if you do not want to start creating a proper child theme, the only other option available to safeguard your changes is to rename the theme as a new standalone. After all, what’s the point of retaining the customised copy of Flexibility 3 since you can never update it?
Thread Starter
zep101
(@zep101)
So, if you do not want to start creating a proper child theme
Isn’t it already too late to make a proper child theme since I have already customized it?
That’s what I meant – unless of course you want to start all over again…
Thread Starter
zep101
(@zep101)
OK, well thank you very much for all your help I have learned a lot. Maybe I will start over again and save copies of my existing changes and just update those in a child. There are not very many.
Thanks again!
