Sixteen Merge

Screen shot of the Sixteen theme

The thing I feared since I fixed some issues in the wordpress theme I use for this blog: it was updated to version 1.3.0.5 without taking into account my bug-fixes [1][2], even though I posted links to them on the support page, so I had to do a merge of the changes, basically re-applying my changes on top of the new version.

The fact that the theme’s source code does not exist in some git repository is really a pain… If you need the patched files, just contact me…

8 thoughts on “Sixteen Merge”

  1. And this is why everyone will tell you to use child-themes!!! That is completely trivial, and helps you to not do this kind of pain again. Do you need some examples?

  2. I haven’t looked at the fixes you send, but since you can redefine every function that is used in the theme, there should be a way to replace the buggy one, too, I guess.

  3. Addition, in this case for example you can replace the sixteen-content-default.php with your copy in the child theme, and thus override the one provided by the parent theme.

  4. Right, but this means that any changes in the file in the parent file will be hidden, no?

  5. Right, but at least you have a chance to make diff on the two and incorporate the updates ;-)

  6. It would certainly make the transitions easier, I’ll look into it when I have time…

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.