Just enabled top domains support for individual Wordpress Multiuser blogs. By default WPMU seemed not be able to do that through it’s management interface, some direct database level hack will be required. I found a complete and workable solution here. I copied the key parts from a post inside for my reference:

1. edit the Domain server for the domainname you are interested in and add a CNAME record for something like blog.domainname.com which points to your WPMU installation.
eg. I added the CNAME blog.clearskys.net to the clearskys.net DNS settings and set it to point to cafespain.com

2. Create a blog in your WPMU installation - it doesn’t matter what you call it for now - use the existing admin system to create it.

3. Add a record in wp_site with the the domain of the new blog. eg. in this case clearskys.net and set the path to /

4. Duplicate the wp_sitemeta entries for your new site (insert into wp_sitemeta (site_id, meta_key, meta_value) SELECT x, meta_key, meta_value FROM wp_sitemeta WHERE site_id = 1 (change x to the id of the new site record created at step 3.

5. Modify the record for the blog you created in wp_blogs and change the domain to the CNAME you created in step 1 (in this case blog.clearskys.net) and change the site_id to the id of the site record in step 3.

6. Modify all the records in wp_xx_options (where xx is the record number of your blog in step 5) that have the domain path, so that it is the same as that set in step 5 (blog.clearskys.net).

7. Wait a bit for the DNS changes to propagate and access the website at blog.clearskys.net, voila one wordpress blog, with it’s own domain running off an installation of WPMU at a different one.

It should only take a short step to have a www.domainname.com to work just as easily.

Step 3 is important for the correct display of the blog.

Step 5 is important for login to the admin interface. if siteid incorrect, it will not able to login.

Step 4 will affect the “presentation” tab in your site admin. incorrect setting will cause that page blank;

Step 6 can be modified from “Site Admin -> blog -> your blog item-> edit”, use this web interface life will much easier.

Popularity: 5% [?]

Share This

Just a while ago, when I try to update from SVN repository, an error happened:

$ svn update main
svn: Checksum mismatch for ‘main/tako-repository-logic/.svn/text-base/project.properties.svn-base’; expected: ‘ea8835ae69173d10e5a1519e5fa8284e’, actual: ‘59f10af8158532e7ddf8d03cbc9cfba4′

Google this problem it seemed many people meet similar problem, however most of them seemed just asking for help, not too many workable answers over there.

It’s very possible that some file was corrupt in the disk, so SVN refuse to continue the work.  I fix this problem by first rename the directory contain problem file(s), and the run SVN again to check out the fresh copy.  If no further problem, I just delete the old renamed directory which contain corrupt files.

  $mv  main/tako-repository-logic main/tako-respository-logic.bak

$svn update main

…

U   main
Updated to revision 17719.

$rm -r main/respository-logic.bak

Since this is a update action, I can just delete the back up folder, if the folder contain some uncommitted files, we will need to synchronize those files to new checked out folder.

UPDATE:  found a blog post “subversion checksum mismatch - easy workaround“, same problem, similar solution.

Popularity: 10% [?]

Share This