Incidentally, you can also now find me on Facebook and Twitter.

My first resource was the WordPress Codex, which pointed me to this post.  I couldn’t get his suggestion to work, however, and didn’t like having a separate .lua file in my WordPress directory.  Thus I wrote my own rewrite rules.

My solution depends on WordPress’ ability to do “fake” permalinks of the “/index.php/permalink” variety.  I don’t know when this was implemented, but it’s in the most recent versions of WordPress.

Before going further, it’s worth noting that I have Lighttpd set up to use mod_simple_vhost for virtual hosts:

simple-vhost.server-root   = “/path/to/www/”
simple-vhost.default-host  = “smidg.in”
simple-vhost.document-root = “/”

With the vhosts already specified (so simple!), the following code is all that is needed to get permalinks working:

$HTTP["host"] == “smidg.in” {
url.rewrite-once = (
“^/(.*\.php|wp-content/|wp-admin/|wp-includes/).*” => “$0″,
“^/([^,]*)/?$” => “/index.php/$1″
)
}

Remember, of course, to turn on permalinks in WordPress under Settings -> Permalinks by choosing the “custom” setting and specifying what you want.

There may be various pieces of the site that this doesn’t work for yet.  If you find any, let me know and I’ll update the rules.  Essentially it catches requests for anything in the three main directories and passes those through while rewriting everything else behind index.php.  Works like a charm!

I told a friend that I would help her move all her old Xanga posts to her new WordPress.com account.  Little did I know how much of a difficulty that would be.  After extensive searching via Google, I finally found what I believe to be the best way.  For the benefit of those coming after me, blow-by-blow instructions are below.

Before I begin, you may want to look at Tim Wylie’s Xanga to WordPress Exporter.  I could not get this to work on my friend’s blog, but it did work on a few random strangers’ blogs that I tried.  Please let me know if you get this to work.

Now, on to my method.  This is a bit complicated (ok, it’s really complicated), but I’ve tried to lay out everything clearly.  The problem is that WordPress.com doesn’t let us import from Xanga directly so we have to install WordPress locally, import our Xanga archives, then export to a WordPress file and upload it to WordPress.com.  So here we go:

1. Upgrade your Xanga account to premium at https://register.xanga.com/premium/. This costs $4 for a one month subscription (make sure to uncheck the “Automatically rebill me!” box) and it’s worth it for all the time you’re going to save.  Just take my word on that and do it.
2. Go to http://www.xanga.com/private/Archives.aspx and get your Xanga Archives.  If this is your first time getting your archives you may have to wait overnight for Xanga to prepare them. Once you’ve downloaded them, unzip the “archive.zip” file to your desktop.  You should now have a folder called “archive” on your desktop.  Inside that is a folder called “xanga” and inside that are HTML files for each month of posts on Xanga.
3. Open a command prompt window by going to the Start Menu -> Run and typing in “cmd” and clicking “OK”.  You should see a black window open up that says something along the lines of: “C:\Documents and Settings\Username\”.
4. Move into your Xanga folder by typing “cd Desktop\archive\xanga” and pressing the enter key.
5. Now combine all of the Xanga archive files by typing “copy *.htm XangaArchive.htm” and pressing the enter key.  (You can now close the command prompt by typing “exit” and pressing enter.)
6. Download XAMPP, a wonderful Apache, MySQL, PHP (if you don’t know what these are, don’t worry) installer for Windows athttp://www.apachefriends.org/en/xampp-windows.html#641.  Choose the “Installer” option when you go to download.
7. When it’s downloaded, run the installer and choose the default options.  This will install XAMPP into the C: drive of your computer.  When the installation finishes click “Yes” when it asks you if you want to run the Control Panel.
8. Go to the folder C:\xampp\htdocs\php\ (you can navigate there by going to “My Computer”, selecting the “C:” drive and then browsing to the “xampp\htdocs\php\” folder).  Open the file “php5.ini”; it should open in Notepad by default.
9. Go to Edit -> Find and type in “max_execution_time”.  Change the value from “60″ to “600″ and save the file.  Close Notepad.
10. On the XAMPP Control Panel, click the “Start” buttons beside “Apache” and “MySql”.   If they start correctly a little green box that says “Running” will appear beside each.  If you are asked to unblock them by the Windows Firewall, do so.
11. Assuming you are allowed to start both of them, try going to http://localhost/ in your web browser.  If a page saying “XAMPP” loads then you’re good to continue.
12. Download WordPress 2.5 from http://www.wordpress.org/download/.  When it is downloaded, extract the ZIP file to your Destkop.  This will create a folder on your desktop called something like “wordpress-2.5.1″ and inside that will be another folder called “wordpress”.  Move the second folder (the one just called “wordpress”) into C:\xampp\htdocs\.  (Do this by opening a new “My Computer” window, selecting the “C:” drive and then the browsing to the xampp\htdocs folder.  Drag the “wordpress” folder into it.)
13. Now go into the “wordpress” folder and click on the “wp-config-sample.php” file.  When it tells you that it cannot open the file, choose “Select the program from a list” and click “OK”.  Scroll down and choose “WordPad” and click “OK”.
14. At the very top of this file you will see something that looks like this
    

    define(‘DB_NAME’, ‘putyourdbnamehere’);    // The name of the database
    define(‘DB_USER’, ‘usernamehere’);     // Your MySQL username
    define(‘DB_PASSWORD’, ‘yourpasswordhere’); // …and password

    Change this to look like this:

    define(‘DB_NAME’, ‘wordpress’); // The name of the database
    define(‘DB_USER’, ‘root’); // Your MySQL username
    define(‘DB_PASSWORD’, ”); // …and password

    As you can see, you are changing “putyourdbnamehere” to “wordpress”, changing “usernamehere” to “root”, and changing “yourpasswordhere” to be blank.

15. Choose File -> Save As in the menu and save the file as “wp-config.php” in the same directory as “wp-config-sample.php”.
16. Download phpMyAdmin from http://www.phpmyadmin.net/home_page/downloads.php. Choose the “all-languages-utf-8-only.zip” option.
17. Once it has downloaded, you will have a file named something like “phpMyAdmin-2.11.7-rc1-all-languages-utf-8-only.zip”.  Extract that to your desktop and it will create a folder called “phpMyAdmin-2.11.7-rc1-all-languages-utf-8-only” with another folder of the same name inside of that.  Right click on that inner folder and choose “Rename”.  Then rename the folder to “phpmyadmin” and move it into the C:\xampp\htdocs\ folder just like we moved the “wordpress” folder there.
18. Now use your web browser to go to http://localhost/phpmyadmin/.  If that page loads, we are good to continue.
19. Look for the “Create new database” option.  Fill in “wordpress” in the box and click “Create.”  It should tell you that “Database wordpress has been created.”  If so, continue.
20. Go to http://localhost/wordpress/. We are now at the WordPress installer.
21. Give your blog a title like “My Xanga” and fill in your email address.  Click “Install WordPress”.
22. On the next page right down the username and password that it gives you.  Then click “Log In” and log into your WordPress.  Leave this window open and we will come back to it.
23. Now we need to download the Xanga importer for WordPress.  The original importer comes from Daniel Kozlowski, but I had to modify it to make comments come in correctly.  You can use either version. See update at end of post for the PHP code.
24. Go back to your WordPress web browser window.  Click on “Manage”.
25. Select the one post on that page (entitled “Hello world!”) and delete it.  Then click on “Import”.
26. Choose “Xanga” (all the way at the bottom).
27. Click “Browse…” and browse to the “XangaArchive.htm” file we created in step 5.  Select it and click “Open”.  Then click “Upload file and import”.  This may take a while.
28. When that page is done loading scroll all the way to the bottom and see if it says “All done.”  If so, it worked, scroll back to the top and click on “Export”.  Then select “Download Export File” and save the XML file it gives you.
29. Now go to your WordPress.com account and log in.  Then click on “Manage” and on “Import”.  Choose “WordPress”.
30. Browse to your WordPress XML file that you just saved and select it.  Click “Upload file and import”.
31. After it uploads, tell it what author to map your import author to.  Click “Import”.  There you go, you imported Xanga into WordPress.
32. Go back to the XAMPP Control Panel and click “Stop” beside “Apache” and “MySql”.  Then click “Exit”. Now you can go to “Add or Remove Programs” in the Control Panel and remove XAMPP.
33. You can also delete all the files you downloaded, though you may want to keep the Xanga archives around just in case.

You’re done! That wasn’t so bad, was it?  Actually, I’ll admit, there are a bunch of places in there that you can get confused.  Feel free to contact me at jim@smidg.in or leave a comment if you need help.

Update: Here is the code for the Xanga importer.  To install it:

• Navigate to the C:\xampp\htdocs\wordpress\wp-admin\import folder on your computer.
• Copy one of the files already there and rename it xanga.php. (If you can’t see the “.php” at the end of the file, just rename it “xanga”.)
• Right click on the file and go to “Open With.” If Wordpad is not in the list, choose to see more programs and select it from that list.
• Replace all the text in that file with the code below. Save it. Now continue with Step 24.

< ?php

//Xanga archive importer by Jeremy Jay
//Borrows heavily from the LiveJournal import script.
//
//Modified for current WP (2.1+) release and for current Xanga archive style by Daniel Kozlowski
//
//ATTN:  unhtmlentities() has been disabled due to it's turning all ". " into ".? "
//       once the post was imported into wordpress 2.1.  Thus, it has been disabled.  If
//       you're using a version of PHP earlier than 4.3, you'll need to un-comment
//       calls to unhtmlentities() in this script.  They are on lines 82 and 120.
//
//ATTN:  I've run into some Xanga archives where the timestamp for a post or comment is
//	    missing a zero.  For example, "12:08" is printed as "12:8".  This script
//	    cannot read those!  Please read through your code if some of the times are
//       coming up weird once you've imported the archive files.

class Xanga_Import {

    var $file;

    function header() {
        echo '
<div>';
        echo '
<h2>'.__('Import Xanga').'</h2>
';
    }

    function footer() {
        echo '
';
    }

    function unhtmlentities($string) { // From php.net for < 4.3 compatability
        $trans_tbl = get_html_translation_table(HTML_ENTITIES);
        $trans_tbl = array_flip($trans_tbl);
        return strtr($string, $trans_tbl);
    }

    function greet() {
        echo '
'.__('Howdy! This importer allows you to extract posts and comments from Xanga Premium Archive files into your blog.  If you do not have Premium but have enough posts to be looking at this, just pay $4 for a month to get the archive and you will at least be supporting Xanga for all the hosting they have done for you.  Pick an archive file to upload and click Import.').'
';
        wp_import_upload_form("admin.php?import=xanga&step=1");
    }

    function import_posts() {
        global $wpdb, $current_user;

        set_magic_quotes_runtime(0);
        $importdata = file($this->file); // Read the file into an array
        $importdata = implode('', $importdata); // squish it
        $importdata = str_replace(array ("\r\n", "\r"), "\n", $importdata);

        preg_match_all('|
<div>(.*?)<hr size=1 noshade/>(
<div>)*?|is', $importdata, $posts);
        $posts = $posts[1];
        unset($importdata);
        echo '
<ol>';

        foreach ($posts as $post) {
            flush();
            preg_match('|^(.*?)</ol>
</div>
|is', $post, $post_title);
            $post_title = $wpdb->escape(trim($post_title[1]));

            preg_match('/
<div>Posted (.*?)\/(.*?)\/(.*?) at (.*?) (.*?)< \/div>/is', $post, $match);
            list($hour,$min) = explode(':',$match[4]);
            switch($match[5]) {
            	case 'AM' : if($hour == 12) $hour = 0; break;
            	case 'PM': if($hour < 12) $hour += 12; break;
            	}
            $match[4] = "$hour:$min";
            $post_date = "$match[3]-$match[1]-$match[2] $match[4]:00";
            echo "Date: $post_date";

            $com = split(' ', $post_title);

            if( $com[1]=='Comments' ) {
                preg_match_all('|
<div>
<div>(.*?)</div>
</div>
|is', $post, $comments);
                $comments = $comments[1];

                $comment_post_ID = $post_id;
                $num_comments = 0;
                foreach ($comments as $comment) {
                    preg_match('|^(.*?)</div>
<div>|is', $comment, $comment_content);
                    $comment_content = str_replace(array ('< ![CDATA[', ']]>'), '', trim($comment_content[1]));
                    //$comment_content = $this->unhtmlentities($comment_content);

                    // Clean up content
                    $comment_content = preg_replace('|< (/?[A-Z]+)|e', "'<' . strtolower('$1')", $comment_content);
                    $comment_content = str_replace('
', '
', $comment_content);
                    $comment_content = str_replace('<hr>', '<hr />', $comment_content);
                    $comment_content = $wpdb->escape($comment_content);

                    preg_match('/
<div>Posted (.*?)\/(.*?)\/(.*?) at (.*?) (.*?) by/i', $comment, $match);
                    list($hour,$min) = explode(':',$match[4]);
            		switch($match[5]) {
            		case 'AM' : if($hour == 12) $hour = 0; break;
            		case 'PM': if($hour < 12) $hour += 12; break;
            			}
          	  	$match[4] = "$hour:$min";
            	     $comment_date = "$match[3]-$match[1]-$match[2] $match[4]:00";

                  if (preg_match('|<a href="http://www\.xanga\.com/home\.aspx\?user=|', $comment) == 1)
			{
				preg_match('|<a href="http://www\.xanga\.com/home\.aspx\?user=(.*?)">(.*?)|i', $comment, $comment_author);
			}
			else
			{
				preg_match('|<a href="http://www\.xanga\.com/(.*?)">(.*?)</a>|i', $comment, $comment_author);
			}

                    $comment_author = $wpdb->escape(trim($comment_author[1]));
                    $comment_author_url = 'http://www.xanga.com/home.aspx?user='.$comment_author;

                    $comment_approved = 1;
                    // Check if it's already there
                    if (!comment_exists($comment_author, $comment_date)) {
                        $commentdata = compact('comment_post_ID', 'comment_author', 'comment_author_url', 'comment_date', 'comment_content', 'comment_approved');
                        $commentdata = wp_filter_comment($commentdata);
                        wp_insert_comment($commentdata);
                        $num_comments++;
                    }
                }
                if ( $num_comments ) {
                    echo ' ';
                    printf(__('(%s comments)'), $num_comments);
                }
            } else {

                preg_match('|
<td style="padding-left:20; padding-bottom:20">(.*?)
<div>Posted (\d{1,2}/\d{1,2}/\d{4}) at (.*?)< \/div>|is', $post, $post_content);
                $post_content = str_replace(array ('< ![CDATA[', ']]>'), '', trim($post_content[1]));
                //$post_content = $this->unhtmlentities($post_content);

                // Clean up content
                $post_content = preg_replace('|< (/?[A-Z]+)|e', "'<' . strtolower('$1')", $post_content);
                $post_content = str_replace('
', '
', $post_content);
                $post_content = str_replace('<hr>', '<hr />', $post_content);

                //Xanga archives have some pretty crappy formatting, so this reduces the string to a single line.
                //THIS WILL NOT REMOVE YOUR OWN FORMATTING.  Any formatting changes you created in your posts
                //are tagged, and thus will not be affected by the removal.
                $post_content = str_replace("\n", " ", $post_content);
                $post_content = $wpdb->escape($post_content);

                $post_author = $current_user->ID;
                $post_status = 'publish';

                echo '
	<li>';
                if ($post_id = post_exists($post_title, $post_content, $post_date)) {
                    printf(__('Post <i>%s</i> already exists.'), stripslashes($post_title));
                } else {
                    printf(__('Importing post <i>%s</i>...'), stripslashes($post_title));
                    $postdata = compact('post_author', 'post_date', 'post_content', 'post_title', 'post_status');
                    $post_id = wp_insert_post($postdata);
                    if (!$post_id) {
                        _e("Couldn't get post ID");
                        echo '</li>
';
                        break;
                    }
                }
            }

            echo '
';
            flush();
            ob_flush();
        }
        echo '
';
    }

    function import() {
        $file = wp_import_handle_upload();
        if ( isset($file['error']) ) {
            echo $file['error'];
            return;
        }

        $this->file = $file['file'];
        $this->import_posts();
        wp_import_cleanup($file['id']);

        echo '
<h3>';
        printf(__('All done. <a href="%s">Have fun!</a>'), get_option('home'));
        echo '</h3>
';
    }

    function dispatch() {
        if (empty ($_GET['step']))
            $step = 0;
        else
            $step = (int) $_GET['step'];

        $this->header();

        switch ($step) {
            case 0 :
                $this->greet();
                break;
            case 1 :
                $this->import();
                break;
        }

        $this->footer();
    }

    function Xanga_Import() {
        // Nothing.
    }
}

$xanga_import = new Xanga_Import();

register_importer('xanga', 'Xanga', __('Import posts from Xanga Archives'), array ($xanga_import, 'dispatch'));
?>

First:

• You’ll want to make sure you have the Battle.net edition of the game installed. Modern processors are literally too fast for the original version, but the bug is fixed in Battle.net. It also adds a few upgrades and enhancements.
• It runs at least through Windows XP (I don’t know about Vista), but you’ll need to have Mac OS 10.4 or lower, as you need classic.

Now, to actually get the game to work over a LAN in Windows XP, here’s what you have to do.

1. Install the game on all the computers you want to play on.
2. Connect the computers over a LAN. If you don’t have control over your LAN (like at college), it’s good to know that the computers don’t actually have to be connected through a router or DHCP server. You can just use a switch (which is also much cheaper than a router) and plug cords from it into all the computers.
3. On all the computers, go to the Network Connections pane in the Control Panel. Right click on the connection you intend to play over (usually “Local Area Connection”) and select properties.
4. On the “General” tab, click the “Install” button.
5. Select “Protocol” and hit “Add”.
6. Select “NWLink IPX/SPX/NetBIOS Compatible Transport Protocol” and hit OK.
7. Go into Warcraft and you should now be able to use the IPX option to create a multiplayer game.

This should be all you have to do on most computers. If, however, you are having trouble connecting to the game, there are a few more steps to do. I found that I could see the game I created in the list of available games, but could not join it. I would get a “waiting for response” notice. If this happens to you, try this:

1. On any computers with multiple network interfaces (wireless, bluetooth, etc.), for each interface you are not using to play over, right click and go to properties.
2. In the list of protocols on the “General” tab, uncheck the IPX protocol. Multiplayer should now work.

As I understand it, what happens is that with IPX either the game or the protocol isn’t smart enough to handle multiple network interfaces. Sometimes packets may get sent to the wrong interface, causing them to be lost and the game not to connect. (Credit goes to this forum for putting me on to the fix. There’s also another fix listed there, but it did me no good.)

Happy gaming!

Please let me know if this works for you; I see a lot of people looking at this, but I don’t know if it helped any of them.� If you had to do something else, let me know, and I’ll update the post with the relevant information.

The other week I took my iBook to the Apple Store to have a hinge replaced and they had to send it off for repairs. For some reason Apple decided to replace the harddrive while they were at it. Luckily, I keep a backup of my files on an external harddrive–as you should too–so it was time to recover them.

However, when I went to open my Quicken file, it decided to inform me that it was “unable to load file.” After a number of hours of research (I’d had this problem before, but just restarted my file instead of fixing it), I discovered that it had to do with the fact that I used rsync to backup my data.

Evidently Quicken uses resource forks to store data in its files in OS X, which are not preserved by rsync. After even further research I discovered a page that vaguely described how to fix the problem. So I decided I should post a description of the solution for those who follow me.

Problem: When trying to reopen a backed up Quicken file on OS X, Quicken says “unable to load file.”

Solution:

Edit (1/8/07): Thanks goes to Clement for pointing out that you will need Xcode 2 and at least OS X 10.4 installed for this to work. You can download Xcode from Apple’s website.

1. Create a directory on your desktop, we’ll call it “dir” and move a copy of your Quicken file in their, we’ll call it old.qdfm.
2. Use Quicken to create a new Quicken data file, new.qdfm, and copy it into the same directory.
3. Open Terminal (in Applications -> Utilities -> Terminal).
4. Go to the directory. (Type “cd /Users/~username/dir/”).
5. Run the command “/Developer/Tools/SplitForks new.qdfm”.
6. Understand that the .qdfm file is actually a folder, and we’ve split the resource forks on the folder and the files in it into hidden files with the same names. So now execute a series of commands:
   “mv ._new.qdfm ._old.qdfm”
   “mv new.qdfm/._* old.qdfm/”
   “mv new.qdfm/Contents/._* old.qdfm/Contents/”
7. Run the command “/System/Library/CoreServices/FixupResourceForks ./”
8. You should now be able to open old.qdfm in Quicken and see your data.

Difficulties:

• When you first open your restored file, it may say “Accounts cannot have subcategories.” This appears to be a one time error, so don’t worry about it.
• All my accounts lost all the category data, where I had classified everything as various types of expense or income. I couldn’t figure out any way to solve this.
• When I went to reconcile an account it seemed to decide I was several hundred dollars off, claiming the account did not match the data from my last statement. I never figured this out either, and it always gave me warnings when I reconciled, wanting to adjust my balance.

So in the end, I started a new file again anyway. But I was able to print out my registers and accounts, so I could have a record of the data. Hopefully this howto helps someone who encounters the same problem. Feel free to ask questions.

Update (1/8/07): Evidently this is a problem that can also occur with Subversion (and, I would presume, CVS) because they also don’t respect resource forks.� Perhaps there is a way of putting the Quicken file inside of a disk image so that when copied it retains all the filesystem information?