use for non-extension PHP/TPL file overriedes and/or core hacks?

[twomice]

This would obviously be a feature add, and I don't know if this idea is compatible with the intent of the extension.

The use cases are these:

1. A recent CiviCRM upgrade exhibits "broken" behavior of some kind, caused by outdated (and modified) files in CiviCRM's "Custom PHP Directory" and/or "Custom Template Directory".

• This extension could display the differences between each overridden file and the current civicrm core file
• This extension could display the differences between each overridden file and the pre-upgrade version of civicrm core file (assuming somehow that this extension could know what that version was).

2. A site owner believes that a previous site admin may have (stupidly/innocently/recklessly) modified CiviCRM core files. Before upgrading, he could use this extension to compare all core files against the publicly released version of those files, and observe the diff for any modified files.

@konadave , are you interested in such features within this extension, or would those efforts be better placed elsewhere?

[twomice]

One more use case:

3. Before an upgrade, the site owner wants to know exactly what are the differences between any PHP/TPL file overrides and the current core versions of those files; this extension could display those diffs.