Chris Hammond
Thursday, January 19, 2012 2:59 PM
So this is Part 7 of my CommunityServer to DotNetNuke blog series, unfortunately it is well over 7 months late, but better late than never I say.
This will be a quick blog post talking about “URLs” and how you can handle the old CommunityServer URLs and redirect them to the proper DotNetNuke URLs. Why would you do this? SEO, bookmarks and existing links. You want people that try to access the CS urls to be redirected properly to the appropriate DotNetNuke URL, be it for a forum post, blog post, or other.
This post isn’t going to cover all the specifics, as there are too many possible variations based on the configuration of your specific website, but hopefully it will provide you an overview of how I handled things in my conversion, and get you on the way to handling them in your conversion.
Views: 594
Chris Hammond
Thursday, August 25, 2011 1:51 PM
Views: 2260
Chris Hammond
Friday, July 15, 2011 2:35 PM
I received an email earlier this week from a company called the MarketGraphics Research Group. They are looking to fill an “Advanced Programmer and Analyst” position, I am assuming out of their Franklin Tennessee office.
If you’re a DotNetNuke developer, or able to quickly get up and running on DotNetNuke (check out the DotNetNuke Training Subscription if you need to get up to speed) you should give the position a gander.
Read the full post for more info
Views: 1255
Chris Hammond
Wednesday, May 25, 2011 1:25 AM
I had hoped to finish up my Community Server to DotNetNuke blog series tonight, but I realized there is just too much less to cover!
I’m working tonight to get the HTTPModule that I created to handle the URL mapping from CommunityServer to DotNetNuke URLs into codeplex. I haven’t touched the code in a few months, and for simplicity sake I had just created using my standard DotNetNuke Module Template, which contains way more information than is necessary for a simple HTTPModule. I’m ripping out the module code and working on cleaning up the project/manifest so it will install properly as just an HTTPModule.
Views: 1080
Chris Hammond
Monday, May 23, 2011 12:51 AM
This is the sixth post in a series of blog posts about converting from CommunityServer to DotNetNuke. It has been far too long since Part 5, apologies for that!
A brief background: I had a number of websites running on CommunityServer 2.1, I decided it was finally time to ditch CommunityServer due to the change in their licensing model and pricing that made it not good for the small guy. This series of blog posts is about how to convert your CommunityServer based sites to DotNetNuke.
Views: 9124
Chris Hammond
Thursday, May 19, 2011 1:12 AM
Views: 1712
Chris Hammond
Sunday, May 15, 2011 11:21 PM
Are you looking for the World’s Best Free DotNetNuke Skin? Well, have I got just the one for you. MultiFunction, you can find it now on Codeplex, or check out the Demo web site to see it in action.
Now for some specifics. Did he really just call it “World’s Best”? Sure, but where’s the proof? What, my word isn’t good enough?
Here’s the background as to why I created the world’s best free DotNetNuke skin. For those of you who know me, you likely know I have a domain problem. Mainly, I have too many of them. Along with that problem goes another problem, too many websites. All of those websites (except for two) are running on DotNetNuke. And they all had different skins, different layouts, different everything.
Views: 2512
Chris Hammond
Sunday, February 06, 2011 12:47 AM
If you haven’t read the previous posts I would recommend that! This blog talks about CsToDNN_2.sql, and assumes you have already replaced the various strings discussed in Part 3. The CsToDNN_2.sql script is used to pull over the Forum threads, not replies, but the original threads themselves.
Views: 15594
Chris Hammond
Tuesday, January 25, 2011 12:34 AM
Two updates on the series in two days? Woah! So before you get into Part 3 of my CommunityServer to DotNetNuke series catch up if you haven’t read the previous posts.
A brief background: I had a number of websites running on CommunityServer 2.1, I decided it was finally time to ditch CommunityServer due to the change in their licensing model and pricing that made it not good for the small guy. This series of blog posts is about how to convert your CommunityServer based sites to DotNetNuke.
Previous Posts:
Part 1: An Introduction
Part 2: DotNetNuke Installation
This is Part 3, Converting Users from CommunityServer to DotNetNuke
Views: 2316
Chris Hammond
Monday, January 24, 2011 12:55 AM
A couple of weeks ago I started off this series, I didn’t intend for it to take this long to get to Part 2, but I’ve had a lot of other things going on.
A brief background: I had a number of websites running on CommunityServer 2.1, I decided it was finally time to ditch CommunityServer due to the change in their licensing model and pricing that made it not good for the small guy. This series of blog posts is about how to convert your CommunityServer based sites to DotNetNuke.
Views: 2214