Jeff Garoutte

c# .net and anything else that happens across my desk

Older posts are broken for the moment

Recently, we did an upgrade to a new version of the .net blog engine.  This update changed how the URLs work and relate back to posts, images, and attachments.  While I am kicking myself for not testing the upgrade before deploying it; I am also a bit surprised that the new code was released without maintaining backwards compatibility of posts that were already published.

This brings me to a cross roads of choice.  Do I...

  1. dig in the code, find the issue and and the backwards compatibility and have to do this each time a new release is issued.
  2. leave the old posts as is and ignore the problem/issue (which, honestly, is irking me)
  3. Fix each post individually.
  4. Write my own blog engine and use it instead.
  5. hope the development team fixes the problem and releases an update.

Given the options, 1 is too much repeated work, 2 will slowly drive me nuts over time, 3 is a bit of work but doable, 4 has a host of issues... and 5.... well...that might happen before 3 or 4 was finished anyway.  Who knows.

#4 Write my own blog engine and use it instead...  while the idea is entertaining, the reality is I like the .net blog engine.  I am not a fan of reinventing the wheel.

Now I don't believe I could write a better blog engine nor do I want to spend the time trying.  But everyone should have a personal project to work on to push their skills and try new things.   A project like a blog engine is an excellent system to do exactly that.   But it is not really what I want to do for a project.  So I am going to look at my options and see what I can do.  The real problem here however is the external links, from places like dotnetkicks.com are now broken to the old posts and writing a new engine, or updating the old articles wont address that issue.  So it looks like I have no choice but to sit down and add in the backwards compatibility for the old URL rewriting system.  The kick here is finding the time to do it. 

Ill look into it and see what I can do.  In the mean time, my apologies to anyone looking for old posts, they are still here, just hiding.

Posted: Oct 04 2009, 21:37 by jeff | Comments (4) RSS comment feed |
Filed under:
Tags:
Social Bookmarks: E-mail | Kick it! | DZone it! | del.icio.us

Comments

metal barn United States said:

metal barn

Nice post I Like your site very well and continue to do so. I have bookmarked your site.



Regards
Nichols

# December 11 2009, 17:41

Denver DUI Lawyer United States said:

Denver DUI Lawyer

Why older posts are broken for the moment. I think that older posts are great.OK you should eliminate your problems.

# December 23 2009, 12:45

mouse cursors United Kingdom said:

mouse cursors

option 5 is the way to go. I'm surprised they released code with this glaring issue. They should fix it soon. Don't waste your time on it.

# January 28 2010, 07:49

Fatcow Reviews United States said:

Fatcow Reviews

Should I get a Dedicated Hosting? Right now I am using ixwebhosting but they keep shutting me down because of high server load. Im getting about 3,000 UV a day. What brand should I get?

# March 01 2010, 10:35

Add comment


(Will show your Gravatar icon)

  Country flag

biuquote
Loading