template.postloop.php child theme in base?

[hughhempel 0]

Sorry of this is covered elsewhere, but I'll be damned if I could find it... I understand that I need to create a copy of template.postloop.php in my "base" theme for PlatformPro... My question is whether or not the ENTIRE file is copied and then modified OR whether ONLY the modifications are necessary... I assume that the child theme file "supercedes" the "platform" file in it's entirety and therefore the whole file is modded... Which leads to the question: Is there an easy way to track these mods so that when the new release of platform shows up the child theme can take advantage? Hope this make sense...

[timlinson 3]

Yep, you'll want to copy template.postloop.php in its entirety. Regarding updates, you can look at the changelog either on your launchpad page or in the theme's root folder. The changes are just bulleted, but you can always ask here for more details on a particular change if something piques your interest.

[hughhempel 0]

Hi Tim, Thanks for the quick reply! My question about the changelog has to do with the mundane mechanics of "upgrading" the platform... Since my new "base" postloop will have perhaps dozens of customizations inside, how does one go about "diffing" the file with the new postloop file that will presumably be part of the upgrade? If we were talking CSS, this would be "simple"... Since a minor tweak to a piece of PHP can make a ton of difference, and since the new (upgraded) postloop file would likely have a combo of new, old, removed, modded code in it, I could imagine a scenario that would not be pretty or easy... Thoughts?

[Simon 248]

Try winmerge if your using windows.