You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long. 7.7 KiB

3 years ago
3 years ago
3 years ago
3 years ago
3 years ago
3 years ago
3 years ago
3 years ago
3 years ago
3 years ago
3 years ago
3 years ago
3 years ago
3 years ago
3 years ago
3 years ago
3 years ago
3 years ago
3 years ago
3 years ago
3 years ago
3 years ago
3 years ago
3 years ago
3 years ago
3 years ago
3 years ago
3 years ago
  1. For a start, why do you want to change from
  2. [MovableType](
  3. You can compare features on [cms
  4. matrix](
  5. I ([cammy](/User:cammy "wikilink")), personally, moved from
  6. [MovableType]( to
  7. [WordPress]( for a number of reasons:
  8. * **Wordpress is Open Source** The biggest reason is that Wordpress is
  9. Free and I can use it for what ever I want! The latest MovableType
  10. pricing is quite expensive and limited, I think. I run a site that
  11. has about five authors on it and the basic license wouldn't cut it.
  12. Someday I hope to setup a site for a commerical product but I'd then
  13. have to get a commerical license.Because Wordpress is Open Source,
  14. it means no licensing issues, no restrictions on use and I get all
  15. the latest updates. My originally MovableType installation was
  16. starting to stagnate.
  17. <!-- -->
  18. * **Wordpress has real subcategories** Like MovableType but it also
  19. has subcategories properly implemented (not some hack). In my old
  20. MovableType installation I had to use multiple blogs to simulate
  21. subcategories. A ridiculas overhead.One critisim I would level at
  22. Wordpress is that it can only manage one site per installation while
  23. MovableType could handle multiple. But thats not really a huge issue
  24. as an installation is much, much, smaller than MovableType mainly
  25. because of the next reason...
  26. <!-- -->
  27. * _\' Templates rather than static pages_\' MovableType creates static
  28. pages which can fill up your webspace quote if you have a lot.
  29. Wordpress uses PHP to dynamically generate pages from an SQL
  30. database. Wordpress can even properly handle real future posts too.
  31. <!-- -->
  32. * **The Code Itself** I\'m no PHP expert but it took me no longer than
  33. ten minutes to work my way around some of the code in Wordpress.
  34. It's nicely arranged, I think and within a few days I was writing
  35. plugins and themes. With MovableType I never got a real handle on
  36. the massive Perl code, and on making plugins, I generally hacked
  37. others work.
  38. * **Not another template language, because it uses PHP!** With
  39. MovableType you have a whole new template language to learn and you
  40. have to build or install countless plugins to extend it. With
  41. Wordpress, it's PHP so it's a full computer language. I've found it
  42. very powerful.
  43. <!-- -->
  44. * **Themes are bloodly brillant** You can drop in "themes" and change
  45. the look and feel of your site with ease compared to MovableType.
  46. I've even created my own Theme from scratch and with PHP could do
  47. some funky stuff (just have a look around!).
  48. <!-- -->
  49. * **Stronger comment spam protection** Built in Blacklists, User
  50. Registeration and Moderation. I know the latest version of
  51. MovableType now has some (if not all) these issues but Wordpress is
  52. free!
  53. <!-- -->
  54. * **Easier to fully backup** At least I have found it is. Because the
  55. look and feel is stored in a "theme" and content in SQL, I could
  56. backup my entire site and move it to another installation with no
  57. problems. With MovableType, not so easy, particuarly if you were
  58. using a BerkleyDB
  59. ([EndOfMovableTypeSaga](/Rbwiki_EndOfMovableTypeSaga "wikilink"))
  60. and you had to copy and paste each template out of the management
  61. UI... ug.
  62. <!-- -->
  63. * Some cool builtin little features like pages, paging entries,
  64. dictionary in the entry field, user levels, etc.
  65. ---
  66. Okay, so you want to move. Start by creating a test site of Wordpress so
  67. you can see if it suits your needs.
  68. [InstallingWordpress](/Rbwiki_InstallingWordpress "wikilink") gives
  69. directions for installing Wordpress on Redbrick. You can set it up in a
  70. subdirectory of in your webspace (normally located at
  71. \'/webtree/\"letter\"/\"username\"/\').
  72. Depending on the complexity of your original site, you\'ll need to do
  73. some thinking before. If you\'ve just used Movable Type for a simple
  74. blog, it a minimal effort to convert it all over but, like myself, you
  75. used it for a picture gallery, software releases, etc. you\'ll need to
  76. do some thinking first:
  77. * **Categories and subcategories** You need to figure out how you want
  78. to use categories in your new Wordpress site. Do you want to have
  79. your seperate blogs as subcategories or do you need to have your
  80. different blogs seperate (which would require multiple installations
  81. of Wordpress)?
  82. <!-- -->
  83. * **Styles and themes** I\'m afraid you can\'t just copy over your
  84. Movable Type look and feel to Wordpress. I made a new Wordpress
  85. theme that looked like my original Movable Type look and feel. Best
  86. advice is to use one of the many (and there is a lot) of free
  87. themes. The [Wordpress
  88. Wiki]( has
  89. several you can try and many links to more resources. Themes do not
  90. affect your content so you can download and try as many as you like.
  91. And they are quite easy to modify if you know a little html, php and
  92. css.
  93. Some effort on your part will always be required.
  94. It is an easy enough process to export entries from Movable Type (in the
  95. admin interface, on the right there is the Export menu item) and then
  96. use the import-mt.php script to import them. Instructions are avaliable
  97. from the Wordpress setup script.
  98. I\'d recommend two plugins to use when importing your entires: [batch
  99. categories](
  100. (read through the comments because you\'ll need to fix it for Wordpress
  101. 1.5) and [Search and Replace]( (which I
  102. wrote to help importing). These should help you arrange your content
  103. correctly in Wordpress.
  104. The best approach for making this move is to create a Wordpress
  105. installation as a subdirectory. If your going to be creating themes and
  106. plugins, I\'d actually recommend two installations. One will be a
  107. _sandbox_ for playing around and the other will be your real site.
  108. Export and import your entries and orgainse the data. Now you can start
  109. trying out themes and plugins etc. The import process does not
  110. necessarily include all the users from your Movable Type install so you
  111. may need to add or modify them yourself.
  112. At this stage you now should have your Movable Type site working away
  113. and seperate from your Wordpress install. My best advice is get your
  114. Wordpress site exactly how you want it before doing anything to your
  115. original site. This could take awhile depending on how much you want to
  116. customise.
  117. Once your ready, make sure to make a backup of your Movable Type site
  118. (in fact, make a backup of everything including the SQL database). Use
  119. the Movable Type interface to delete the blogs and then delete Movable
  120. Type. Now your ready to move or link your Wordpress site.
  121. It is very, very easy to move your Wordpress directory. Make a copy of
  122. the Wordpress directory you want to move in the place you want to move
  123. it. Then open up the Site Admin and modify the URI of the site as
  124. required. Then just delete the old copy. Content is preserved in the SQL
  125. database.
  126. You can also have Wordpress installed in the root of your webspace, no
  127. problem. I wouldn\'t recommend it myself, in case you want to have
  128. different or alternative \"blogs\" and sites.
  129. The best approach is have Wordpress handle the site in a different
  130. directory, namely the root of your webspace. This article explains how
  131. to [install WordPress files and blog in different
  132. directories](
  133. ---
  134. The [Wordpress forums]( and the [Wordpress
  135. wiki]( are the best resources for
  136. Wordpress. Any questions, suggestions and thoughts, just modify this
  137. topic and leave a message.
  138. Good Blogging!
  139. [Category:HowTo](/Category:HowTo "wikilink")