• I am in the process of converting my blog from Movable Type to WordPress. I have been able to get everything imported and running under WordPress. I have also set up WordPress permalinks to the default setting, which matches the Movable Type permalinks that I am already using, with the exception that WordPress uses dashes unstead of underscores in archives that have titles that contain spaces. I would like to point my blog subdomain name to my WordPress directory so that I can delete my Movable Type installation. Unfortunately, this dash/underscore difference is giving me problems. Is there anyway that I can change WordPress’s behavior? Perhaps a better way would be to use a rewrite rule in .htaccess. However, I haven’t been able to get this working. Any ideas?

Viewing 10 replies - 1 through 10 (of 10 total)
  • Thread Starter cbtlsl

    (@cbtlsl)

    Yes, I have. But this isn’t quite what I want to do. I have a subdomain that I have pointing to my MT blog. I want to change this subdomain so that it points to my WP blog. As such, keeping all of my MT individual archive entries with redirects to WP won’t work.

    the function sanitize_title(); in the file functions-formatting.php
    is what cleans the post titles. So you could modify that function, delete the imported entries and then import them again, so they will have “wordpress_is_ good” kind of titles, the way you want them.
    I wish I could tell you how exactly to change the function, but I don’t want to break anything on your blog, and I don’t want titles to change on mine. ??

    Thread Starter cbtlsl

    (@cbtlsl)

    Thanks, this is what I am looking for!

    i’m migrating from mt as we speak, and i also am keeping the dirify settings from mt, so that the permanent links stay, umm, permanent.
    what i noticed is that even after you alter the sanitize_title function so use _ instead of the annoying -, wp-blog-header.php will try to do some sanitizing itself when it tries to load entries with the $name param and substitutes $name = preg_replace('/[^a-z0-9-]/', '', $name); our lovely – for nothing.
    in the future, i would like to see _ as an option and not having to hardcode 2 files in every upgrade of wp.
    that’s the bashing bit, as for everything else i’m loving it.

    wp-blog-header now includes underscores in the name preg_replace. All of our rewrite rules accept underscores as well. Dashes, however, are preferred by Google. And, to paraphrase Sarah Vaughan, “ Whatever Google wants, Google gets.”

    It should be known that underscores are not search engine friendly. Google and others see an underscore as a part of the sentence, as one word for entire title. Dashes are seen as spaces ??

    Google will catch up with the new urls for your entries/blog pages soon enough (it took 2 weeks for me), so you don’t have to worry too much, and using – instead of _ generates approx. 180 google referrals a day, as opposed to the 20 before ??

    It’s not all about Google — there are plenty of people out there linking to my old MT entries with “_” permalinks. I’m gonna deal with this by providing a redirect file for my 1000+ old entries; it’s certainly not a big deal. But just wanted to clarify the reasons why people don’t want to leave old links hanging. ??

    Okay, this is quite some time after the original, but I am a relative PHP n00b and am moving from Movable Type to WordPress. However, some external sites are linking to entries within the Movable Type permalink structure, and I can’t quite figure out how to edit the function sanitize_title.

    It’s going to take quite some time to move over though as it’s a complex site (https://theliberation.net) even with MT, and I’m still trying to figure out a few bits and pieces. However, the first pressing need is to make the permalinks underscores and not dashes.

    Good timing. I noticed this plugin earlier. Haven’t tried it myself, but it looks like it might be what you’re after…

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘MovableType Permalinks vs. WordPress Permalinks’ is closed to new replies.