Quote:
Originally Posted by findingpeace
I know it's bad practice to edit the physical vB files, but I've done it for a few, and I can't for the life of me remember which ones, but I know they're important! Is there a scanner or plugin that will find which ones don't match the original 4.2.1 files, before I upgrade to 4.2.2?
Thanks!
|
We've altered a bunch of default vbulletin files as well with our site. The way to check which files have been altered is to go into admincp, and go to Maintenance->Diagnostics and choose the Suspect File Version. Any file that is reported as not having expected contents has been edited.
Another way we keep track of which files have been altered is through the use of a version control system, we use git. Our system actually has two repositories setup, one contains vanilla vbulletin files which we use as the source repository (is not web reachable) and the second repository is the actual forum directory and is a downstream repository. Any changes to code/images/whatever on the site are then tracked and when it comes time to upgrade vbulletin we can do a git rebase which applies (or at least tries to apply) all our changes to the new code in the new version.