Upgraded to Drupal 5

I just finished the first pass at upgrading this blog to Drupal 5.0. Looks like almost everything is working right out of the gate. I hit a few minor glitches:

  1. spam.module has a strange bug, where it fails to display nodes with ID larger than 1519. Node 1520 and higher failed to display at all until I disabled spam.module and switched to Akismet.
  2. CCK – my bikelog is MIA. not the end of the world – actually, I’d hoped to just go ahead and retire it and do what normal/sane people do: get a cyclecomputer. But, enough people find their way to that page from the CCK/Calculated Fields page that I’ll give ‘er a shot when I get a chance.
  3. The K2-derived theme I’d been using borks under D5. Again, not the end of the world. I’ll take a look at upgrading it later. For now, I’m kinda liking the new default Garland theme… Theme updated. Borrowed snippits from Garland to get the scripts etc… properly included.
  4. TinyMCE appears to be shy. It’s installed and enabled, but refuses to show up. Again, not the end of the world, as I’d just as often write raw text/html or use Performancing for Firefox, which works just fine.
    Update: I grabbed FCKEditor, and it’s doing a decent job. I miss having the user setting that let me turn off rich text editing by default, so it doesn’t bork embeded code, but maybe FCKEditor doesn’t do that…. Bork embedded code, I mean.
    I’m really not a fan of FCKEditor’s lack of semantic markup (using br br instead of wrapping paragraphs in p elements, for example) but it works.
  5. The code I’ve been using to automatically generate the colophon (list of active modules, etc…) borks under Drupal 5.

There may be other gotchas. I did the upgrade on my desktop box, then moved it into place so I’m relatively sure nothing is pouring smoke…

I just finished the first pass at upgrading this blog to Drupal 5.0. Looks like almost everything is working right out of the gate. I hit a few minor glitches:

  1. spam.module has a strange bug, where it fails to display nodes with ID larger than 1519. Node 1520 and higher failed to display at all until I disabled spam.module and switched to Akismet.
  2. CCK – my bikelog is MIA. not the end of the world – actually, I’d hoped to just go ahead and retire it and do what normal/sane people do: get a cyclecomputer. But, enough people find their way to that page from the CCK/Calculated Fields page that I’ll give ‘er a shot when I get a chance.
  3. The K2-derived theme I’d been using borks under D5. Again, not the end of the world. I’ll take a look at upgrading it later. For now, I’m kinda liking the new default Garland theme… Theme updated. Borrowed snippits from Garland to get the scripts etc… properly included.
  4. TinyMCE appears to be shy. It’s installed and enabled, but refuses to show up. Again, not the end of the world, as I’d just as often write raw text/html or use Performancing for Firefox, which works just fine.
    Update: I grabbed FCKEditor, and it’s doing a decent job. I miss having the user setting that let me turn off rich text editing by default, so it doesn’t bork embeded code, but maybe FCKEditor doesn’t do that…. Bork embedded code, I mean.
    I’m really not a fan of FCKEditor’s lack of semantic markup (using br br instead of wrapping paragraphs in p elements, for example) but it works.
  5. The code I’ve been using to automatically generate the colophon (list of active modules, etc…) borks under Drupal 5.

There may be other gotchas. I did the upgrade on my desktop box, then moved it into place so I’m relatively sure nothing is pouring smoke…

11 thoughts on “Upgraded to Drupal 5”

  1. Thanks, Bill! That works like a charm!

    And caching appears to be making comments disappear for awhile before they show up…

  2. Hi D’arcy,

    good job – today finally finished my way overdue migration of
    my oldest weblog, previously run on MT 2.65 (!!!) the original perl 2003 version 🙂

    see more at

    http://weblog.cemper.com/a/200702/05-running-drupal-51-finally-an-exhausting-migration-from-mt265.php

    Finally I could also freshen the layout and like it VERY VERY much…

    let me know what you think!

    cheers,Christoph

    PS: comment_notify migraton still pending… maybe we get your weight/call priority problem fixed in DP5 ????

  3. Christoph – looks very good. Garland rocks. I’m toying with moving to that myself…

    If there’s anything I can do to help get a working comment_notify for D5, let me know.

  4. Depends on what you want to do. If you just want to run a blog, WordPress makes the most sense (this blog is now running on WordPress 2.5). If you want to do some really funky application type stuff, then Drupal is totally the way to go.

    For individual blogs, I highly recommend WordPress.

    For high-end websites and complicated content management, I hightly recommend Drupal.

    Depends entirely on what you want to do.

Comments are closed.