***Dave Does the Blog evolves into WordPress.

I get all busy over the weekend and ***Dave goes and switches blogging platforms on me. He’s made the jump to WordPress from MovableType and it’s a much needed improvement. WordPress has come a long way from back when I tested it out as a replacement for MT. Depending on how much it’ll cost to move to EE 2.0 when it’s released sometime this year I might be making the jump as well.

Go check out ***Dave’s shiny new digs and let him know what you think.

10 thoughts on “***Dave Does the Blog evolves into WordPress.

  1. I have been using WordPress.com and .org for over a year now and I love it.  I tried the other web based ones and didn’t like them as much as WordPress…

    I can’t comment on the blog though since I never saw it before he switched.  grin

  2. Thanks, Les.  I’m greatly pleased with how it’s working out, though I will almost certainly be changing themes in the near future (for some of the oversized graphics I’ve used).

  3. I have to admit that the long delay in getting EE2 out the door is starting to bother me and I also expect that their upgrade price to be a drop in the bucket for commercial clients, but outside of my impulse buy range. I’ll make a decision once it’s out and the pricing is set. If it’s not too painful I’ll upgrade all or part of my licenses; otherwise I’ll stick with EE1.6 and eventually migrate back to Drupal—which has also come a long way since I last used it.

  4. WordPress for self hosted sites is still free after all this time.  And it includes pulling posts from most blogging platforms. 

    WordPress.com is WordPress’ answer to blogger…they host a limited version of the software for you.

    I lurvs me some wordpress.

  5. My two biggest problems with WordPress back when I assessed it for SEB were:

    1. The templates were part of the actual script which meant updating the script wiped your template right out unless you transfered it over by hand to the new script.
    2. The lack of support for multiple blogs on a single installation.

    There were a number of other minor issues, but most of those have been sorted out either through updates to the script or plugins. Of the two I mentioned above the first issue was corrected quite some time ago. The second one still remains. Though they have started a branch of WP that supports multiple blogs, but I’m leery of using branches for fear of them falling behind the primary branch and there are apparently a number of themes and plugins that will not work with the multiple blog version of WordPress.

    That said, these days I tend to recommend WP to anyone who asks me what blogging platform they should use. I suggest starting with WordPress.com and then moving to self-hosting if they feel they have a penchant for blogging.

    The prospect of trying to migrate EE over to WP is daunting to say the least. The easiest solution would be to make a template that outputs in the MovableType Export format and save everything out that way and then re-import it into WP. I’d lose a few things in the process, but it’s doable.

    The other option would be doing what some other bloggers I know have done and simply start over on the new platform and not worrying about all the crap I’d be leaving behind. My pretend Internet girlfriend has done that at least three times now.

    And, ***Dave, tags are spur of the moment things. Nothing at all like getting an Oscar.

  6. The prospect of trying to migrate EE over to WP is daunting to say the least. The easiest solution would be to make a template that outputs in the MovableType Export format and save everything out that way and then re-import it into WP. I’d lose a few things in the process, but it’s doable.

    I haven’t done this particular migration yet, but getting the data moved is almost never the most serious issue.

    If WP supports the MT format, then that’s definitely the way to go if it comes to that. I would not set up an EE template for the export, though, unless you can find a way to not render the original fields as HTML. Cloning your EE install and changing the field formatting to “None” might do the trick.

    Once this goes beyond the outline of a contingency plan, you can always set up a Linux server in VMware or VirtualBox and see how tricky a migration might be.

    I myself keep an eye on Drupal. I keep meaning to check out MT4, but I can never work up enough motivation to take it for a spin.

    Out of curiosity, ***Dave, did you consider MT4 or were you running it? And what prompted you to move off MT?

  7. I was actualy running MT 4.01.  I’d considered (for many months) upgrading to the current 4.2x versions (so that I could make a clean start on templates), but never got around to it.  As painful as the change to WP was, I don’t think the upgrade would have been easier.

    The move from MT was prompted by spammer-related performance issues.  With the system inefficiency of the Perl/CGI scripts, esp. with MT’s dynamic publishing system, it was just bringing my site to its knees whenever the Baleful Eye of Spammers turned my direction. 

    Plus, most of the stuff they were working on in expanding MT didn’t really make me go ooh and aah.  And I was tired, whenever I was looking for a plug-in to add some new feature, of sifting through a half-dozen for WordPress until I found one for MT … and only then finding out that it was designed for MT3.

    I was surprised to see that there were no notes in the WP codex for converting from EE to WP (there are for any number of other systems).  I think your tactic sounds like the right one, if you ever make that decision, Les.

  8. Thanks for the info, ***Dave. Guess I can remove MT4 from my shortlist.

    The EE forum and wiki has information about migrating to/from EE. I’ve never seen numbers, but I doubt EE is used widely enough to warrant conversion notes on other platforms.

    Running multiple blogs off a single code base is convenient, but in the case of WP I’d prefer to run multiple blogs rather than a branch. With Drupal, you can do really fancy things with regards to sharing the installation files and databases or even database tables. It’s a headache when you upgrade versions, though.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.