If you do a radical update of a theme, can you prevent people from unintentionally upgrading until they have read and approved a warning telling them the changes might break their child themes?

Or, is it best to fork your theme and call it Theme2 or something similar?

1 Answer 1


If you're making a radical change in a framework style theme, I would most definitely fork it into a new & separate version. Particularly if it's going to have a potentially adverse affect on a lot of existing child themes.

I'm sure I could come up with a creative way to warn your users of a change -- but that'd be more easily done if you had some "phone-home" functionality, for messages, in your existing themes codebase to provide warnings / news rather than trying to do it after the update.

Perhaps you could do an intermediate update that won't harm child themes, that also displays news and information about the new version?

  • validates what i was thinking. i just wanted to see if there was a hook that i didn't know about. thanks! Aug 4, 2012 at 22:01

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.