Support » Requests and Feedback » WordPress Vs. MovableType?

  • Hello! This might not be the right forum for this, but I’m seeking some feedback. I’m currently a *very* new MovableType user and new to the blog world as well. I’m a bit frustrated with MT for a few reasons and was thinking about trying out WP. Are there any of you here that have used both? What are the differences? If you have used MT what made you switch?

Viewing 8 replies - 1 through 8 (of 8 total)
  • No Rebuilds.

    I’ve recently switched from MT, and I won’t be switching back. 🙂
    The biggest reason why I think you should use WP is the community. If WP doesn’t do what you want it to “out of the box,” experts on this forum almost always come up with a solution. There are a lot of active and enthusiastic community members here determined to improve WP–and, unlike MT, the community can improve the product; WP is open-source, which means that any developer can make suggestions and contribute improvements. While WP is still relatively young, I have no doubt it will surpass MT in every capability. 🙂

    Firstly, Nice decision if you’re thinking to move to WP. I have moved from MT to WP a couple of days back, and have no regrets whatso ever. WP is just beautiful.
    The best part of it is No re-building as sushubh points out.
    Its very very simple to configure.
    Setting up Permalinks was really simple.
    You dont need any hack for converting 🙂 into smilies. All inbuilt.
    AND the most important reason of my move was “Disk Usage”. I dont remeber the links but read it in a couple of pages that if you keep blogging for a year or two and when you have over 500 entries, that when you really notice how much Disk space MT uses, coz it physically stores every page, whereas WP stores them int he DB, and builds the pages dynamically.
    Hope that helps. Woohooo.. Word Press Rocks!!

    Forgive me for tooting my own horn:
    It’s a chart that compares a bunch of different features of MT and WP.

    No need to ask for forgiveness. Your chart is serving it’s purpose, after all.

    I switched from MT to WP about a month ago, before the recent licensing issue.
    I ended up going with WordPress because:

    • No rebuilds
    • The community and the developers. When something seems to be wrong or a bug is found, they fix it right away. Also, I was very impressed with the fact that they did communicate and did come here to help the rest of us out. 🙂
    • The Typekey issue (I moved from Blogger because of having to depend on another server or service to post and when they were down or my comments server was down, nobody could use it. And I was not all that keen on having people have to register with a service they might not want to register with to leave a comment on my blog. Also, at the time, the rumor was that the Blacklist was going to be obsolete and there would not be a new one, but that rumor has been dispelled after I made the switch. I think the solutions that WP has for comment spam are pretty good and much simpler than having to use Typekey.)
    • My wanting to get a sense of PHP and wanting to learn more about it.
    • Just the fact that this program is so simple, but yet it does everything I want it to do.
    • Server space. My old MT blog took up a lot of space on my server. MT grew to become more complicated than it really had to be, IMHO.

    When I was looking into WP, the only disadvantage I found was not having multiple blogs on the same install. But there were so many advantages, that I decided that not having multiple blogs on the same install was something that I could live with.
    I have been nothing but happy since I switched over. My husband took a look at WordPress after I got it up and running and was so impressed with it, he made the switch, too.

    Mark (podz)


    Support Maven

    Or follow links in the Dev Blog or from Photomatt’s page ( and see why some ‘movers and shakers’ are making the switch 🙂

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘WordPress Vs. MovableType?’ is closed to new replies.