This is all ot do with each individual theme and how they implement it. It can’t be done by the WordPress core alone.
You are right that any changes made to the themes files will be over-written on the next update, and that’s why you should always develop changes in a child theme. That way you never have to worry about your changs being over-written.
OK thanks.
I have never created a Child Theme before but I can see from your link that your changes are unaffected by Theme updates.
Can you be sure tho that your child theme will always do what you want it to the next time the parent Theme changes?
So if not you have to weigh whether its worth the hassle of implementing a child theme if it needs testing every time the parent changes.
You’ll never be able to guarantee that. No matter what, if some functionality in the parent theme changes, then it will need to be adopted by the child theme. The default WordPress themes that are used here are normally pretty good with that though and don’t break things much from what I’ve seen.
Thanks again.
Think I might go to the Theme’s authors and see if they have a suggestion. Who knows they may put it in their next update!
I think we are done, appreciate your time on this.
I’ve had a look at the code of the plugin, and there is a setting to turn that message off so you can do that. BUT, the setting is still set to on as a default, which I do know os frowned upon by the plugin moderators, so I’m sure that they’d like to know about it so that they can make sure that this plugin changes it’s default settings so that others don’t get into the same problem as you. 🙂
Which Plugin are you referring to?
Damn… Sorry, I had to many windows open at once and responded in the wrong thread.
