If you Hack, you should Track
If you read my previous post, you’re already aware that I’m fairly new to WPMU, and this post is directed to those users who are just starting to find their way into the multi-user WordPress environment. Following is a quick tip that will help you immensely in the long run, but first some background information.
Through my first experience with WPMU, I have spent many hours searching the forums while trying to determine the best plugins and code hacks to accomplish the goals of the site I am developing. I’ve downloaded dozens of these plugins and have made many several changes to WPMU core files. During this process, I was working with version 1.3.3 and then came a new version, 1.5 RC1, and then yet another, the official 1.5.1 version which integrated the changes that were made to the standard WordPress 2.5.1 backend. As you might imagine, with all these upgrades, and with me including code hacks in between, things can quickly get out of hand and confusing.
The purpose of this post is to remind all new WPMU users, and even veterans, to TRACK YOUR CHANGES. This may seem like a no-brainer, but with as many code hacks as I’ve tried to get things working the way I want, if I wasn’t tracking what I was doing, I would quickly become lost when I needed to upgrade and preserve my changes, or to troubleshoot when something goes wrong.
Tracking my changes couldn’t be simpler. I just keep a simple text document on my local system that I enter the changes into. When it’s time to upgrade or refresh myself on what changes I’ve done, I just open it up and have a look.
I hope this helps make your WPMU experience just a bit easier.
p.s. The WPMU site I’m working on is still in development, but will be open for beta testing soon. Please stay tuned here and also at here for further announcements.