Renaming theme and future updates

  • Resolved woody2016

    (@woody2016)


    7 years, 2 months ago

    Hi Anthony,

    Thank you for Quark, I have used it as a building block with a child theme for a number of sites and really find it exceptional.

    My question: If it is used as a modified parent theme, as a theme in its own right and renamed, is there a simple method I can use to apply any future Quark updates to the ‘branded’ theme.

    Any advice appreciated,
    Nel

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter woody2016

    (@woody2016)

    No – replies so I have looked into this and will just compare any subsequent change log with the original version used for the theme.

    Theme Author Anthony Hortin

    (@ahortin)

    Hi Nel,

    If your forked my copy of Quark on Github you may be be able to perform a Pull of any future changes I make. If you’ve modifed your forked version, you’d need to be careful of what updated files you sync as you obviously wouldn’t want to overwrite your own modifications. As to how to only Pull in certain changes (as opposed to all changes), you’d need to ask someone with more Git experience than me, sorry.

    The only other option would be to use a Diff program (e.g. kDiff3 is one example) to compare what files have changed and then migrate the changes to your own theme. Again, you’d need to obviously take care not to overwrite your own changes.

    They’re about the only options I can think of at the moment. Unfortunately, there’s no real easy solution, which is why it’s a good idea to use child themes if you can.

    I hope this helps ??

    Thread Starter woody2016

    (@woody2016)

    Hello Anthony,

    Further to your message and the options you outline. I am thinking that I will return to the child method given your advice. The risk using a ‘stet’ template from a renamed Quark as a basic building block may be too great otherwise.

    My customer, for some reason, wanted his ‘own’ theme but its just too impractical given any issues that may arise from woocommerce / wordpress core system updates etc. and my own limited experience. it was a bit worrying when i looked at typical change logs!

    Thank you for the advice (and especially Quark), much appreciated.
    Nel

    Theme Author Anthony Hortin

    (@ahortin)

    Hi Nel,

    Thanks for the kind words. I think that sounds like the best way to go (using a child theme).

    I understand how frustrating customers can be sometimes, especially when trying to explain your reasons for doing something one way, compared to another. You can tell them that they are getting they’re own theme (albeit a child theme). The child theme simply utilises another theme as well. The benefit for them is that you haven’t needed to develop something from scratch and you’re utilising code that has been used and tested by thousands of others. It’s similar to the reason why you’re using WordPress, rather than writing your own custom CMS. Plus, as you know, it will be significantly easier to update in the future, if needed. ??

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Renaming theme and future updates’ is closed to new replies.