Divi WordPress Theme

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.

WPMU Core File Edits

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.


  1. You should consider running your copy of WPMU off of Subversion. Then generating a patch file of changes is as simple as svn diff, and the patch file with a little editing can usually be applied to the next version when you upgrade the core files.

  2. Austin,

    Thanks for the advice. I haven’t had any experience at all with Subversion. I will look into using it. If you know of any good tutorials, or can share your methods, I would be very grateful to be made aware of them.

  3. Here are two introductions to WordPress and subversion:


    You can view a list of the WPMU versions available over Subversion with the following command (remove the spaces between the h t t p letters):
    svn list h t t p://svn.automattic.com/wordpress-mu/tags/

    [Aside: You might want to warn commenters that they will lose any submitted comments with links that have h t t p in them because of an “edublogs” spam filter.]

  4. Hi
    I need a php expert. He will help me editing signup.php and wpmu-functions.php . He will just edit no writing new codes nothing! ( maybe little )

    One who helps me solving my problem can take one these domains below.( please only php experts. ) My e-mail is written in my info.


    min-us.com (75.500.000 Google results.!)

    sawc2010.com [ south africa world cup 2010 sawc2010.net is microsoft’s domain name. I have $250 bid on afternic.com but I didnt sell it. please check. If you want this domain you must promise me to help if I have a problem in the future! 🙂 ]

  5. A legendary change log – I am horrible about tracking hacks, but when I do, I use a legend that I found included in the Joomla change.log file. I think it was Joomla, but whatever it was, here it is. This is really handy when your log gets reallly long. Of course you can use whatever symbols you want if you don’t like these.

    * -> Security Fix
    # -> Bug Fix
    + -> Addition
    ^ -> Change
    – -> Removed
    ! -> Note
    = -> Reminders