How would I compare and remove hacks to core?

I have been put in charge of a site that have a lot (and i mean it) of core hacks,
some are pretty easy, some are really hard to spot (like removing a do_action on the_content.

So, my question is , how i would and remove the hacks the previous maintaners did, while adding the new features requested.

Read More

Should i go and fix as soon as i spot them, or actively search for any hack in the core? (Side-Effect of the core hacks,can not update wordpress or it will completely break and a lot of features will be “removed” effectively putting the site down)

Related posts

Leave a Reply

2 comments

  1. Pull down the copy of WordPress from your client’s server to your local.

    Download a clean zip of the version of WordPress your client has installed. http://wordpress.org/download/release-archive/

    From there, you will need to use a file comparison tool (i.e. Diff on Linux). You can also use GIT to find the difference in folders by creating a GIT repo of the hacked WordPress, then overwrite the files with the new WP and GIT will track them and show you the differences. Github for Mac can make easy work for you.

  2. To add to what Brain said, I think using a visual IDE that shows git/svn changes helps a lot, and also allows you to save all the changes.

    Here is a screenshot of what a git compare looks like in netbeans 7.0. ( the git integration is still new but so far seems to work quite well). It works with SVN, CVS, and Mercurial too.

    enter image description here