First Download the DotNetNuke software. If you’re not doing any development aside from skins and such, grab the Install Package. This doesn’t mean you won’t be able to install modules. The other ones are more for developing.

IIS 7 Settings For DotNetNuke

Install IIS 7 if you haven’t enabled it. You can do this through Vista’s Control Panel under programs and features. On the left hand side your see something that says Turn Windows Features On Or Off. In the next dialog box, make sure you have these items checked. They aren’t all necessary but, you should have IIS Management Console, and ASP.NET which will enable a couple of other checkboxes. Also, a couple of items under Commone Http Features.

Create Database in Microsoft SQL Server 2008

right-click databases and select NEW DATABASE

Under General, Type in a the name of the database as whatever you want (typically DotNetNuke) but, remember what it is because, you’ll need it later.

Click on the button to the right of the Owner to browse for an owner. The options available will depend on whether or not you used the Native Windows Authentication mode or SQL Server and Windows Authentication mode. Basically, with Windows Authentication mode you’ll be using the credentials of the Windows Server Box you are using as opposed to using a separate list of SQL Server users kept within the SQL Server database.

Under the main category of OPTIONS on the left, I chose the compatibility level to coincide with SQL Server 2005. I’m not sure effect it would have if any to choose compatibility with SQL Server 2008 but, DotNetNuke 5 should be coming out reasonably soon so, that should support it. Anyway, like I said, this is just the quick and dirty version.

I left the rest of the options as default. These instructions are more for a local development stand-point but, so I can’t guarantee security. Talk with your host to ensure that there aren’t any giant holes saying “HACK ME PLEASE :)”

Now the most important road block I think most people will run into including myself is all about permissions to files and directories including being inaccessible or non-writable and/or bad credentials to your SQL Database usually having to do with mispellings or targeting the wrong user with the wrong permissions.

SQL Server 2008

If you’re having problems connecting to the SQL Database DOUBLE and TRIPLE check these settings if you’re having problems and make sure you’re calling the right DATABASE NAME. If the SQL Server is on the same machine as the web server then the SQL Server name should be LOCALHOST. Also, you might see “Login failed for user ‘NT AUTHORITY\NETWORK SERVICE’. Make sure to right click on your database and goto properties > permissions > View server permissions. Look for ‘NT AUTHORITY\NETWORK SERVICE’ in the Logins or roles area. If you’re having problems and are troubleshooting permissions. Grant all of them to ‘NT AUTHORITY\NETWORK SERVICE’ but, remember to go back and change them when you figure out the culprit.

Now a little detail for the issues with permissions to files and folder. I recieved a number of errors such as “Access to the path Compression.config’ is denied” or some other file wasn’t writable. I’ve seen some on the net on other forums saying to move these files from the config directory to the root. Sure, you might get some random concoction to work like I tried to do on math tests in school but, the reality is, it should work if you’ve setup permissions properly. You should be able to install IIS 7, create an SQL Database, throw the files in your web root, set permissions on the database and navigate to the fully qualified domain name such as http://localhost/ or http://www.whateveryourdomainnameis.com/ to start the installer. You may get an error dealing with the NETWORK SERVICE on the actual permissions of the root folder which is different than the credentials of the database.

Also, under default application pool, your .NET Framework should be at least in the 2.0 or above. And your Default Website should be using that default application pool by default or you’ll have to right click on it to add the pool.

Under Default Document in the IIS Manager. Make sure you move the Default.aspx to the top to speed up performance, otherwise it will check for all of those other files first.

Ok everyone, like I said quick and dirty. Well as quick as quick can be when dealing with computers but, I hope this helps. I couldn’t find any good articles for my problems so, I wrote this. I can’t stress enough, permissions are savior to this whole installation. Also, just to make sure these aren’t causing the problem, try re-starting your computer and/or restarting the IIS server and SQL Server. I know in MySQL you have to reload privileges and whether it’s documented or not with Microsoft’s SQL Servers, it’s always good to try. I’m sure we’ve all had to “power cycle” something over the phone on tech support. =8o] It does work sometimes.

Hopefully I saved you 30-50$ on a book. If you have any questions, feel free to comment or shoot us a message. You can always call us and talk to a real live person too. That’s a rare these days eh. LOL go figure. I’m sure we could save you more on design and development as well. When you need it, we’ll be there. If you build it, we will come. ;o)

So you may already have figured out how to apply the custom styles to the FCK_editor in Dotnetnuke DNN so it reads your css files and displays the styles accordingly while editing Text/HTML in the editor. As you noticed though, the link file still stays the default blue color. In order to stylize these links do the following:

Go edit the file: wwwroot > Providers > HTMLEditorProviders > FCK > FCKeditor > editor > css > fck_editorarea.css

Open that file and edit the lines 47 - 51. These current CSS styles for DNN FCK editor style the links. Delete the syles or change according to your preference so it reads the link styles in your skin.css or default.css files for your Dot Net Nuke site.

Need more info into stylizing the FCK Editor on your site? Let us know.

So, how do you get rid of those annoying little arrow icons before each link in your blogroll and your categories sidebar in WordPress? Alright, I had to post something about this issue as I haven’t seen much on it. It’s a lower level CSS function that although useful, because of our favorite browsers like Microsoft’s Internet Explorer not supporting it, we tend to forget to check it. Look in your style sheets for this code and delete it or comment it out and you’re good to go. It’s too bad it doesn’t work cross-browser as it would be a nice tool to use.

.entry ul li:before, #sidebar ul ul li:before {
    content: "\00BB \0020";
}

As an alternative to list styles images, if you have links in those lists, try styling the <a> tag and put a background image in it with padding on whatever side you choose to put the image on. Here’s an example of what that might look like.

a {
    background:url("mybullet.png") top right;
    padding:0px 10px 0px 0px;
}

Ok, with an unlimited amount of resources you had to  know it was coming. What does google want with a genetics expert? Perhaps to see how many people are genetically predisposed to certain keywords that will be prone to clicking on those juicy cheese burger ads? Maybe, Match.com could use the genetic index to help their users find a better match. Anyway, it’s interesting to say the least. I can only imagine what they’ve got up their sleeves by indexing and capitalizing on human DNA. If you think you have the right “genes” for the job. Be sure to check it out here.

While I have been designing / coding Dot Net Nuke skins for the past 6 or so years, there are still days I learn something new or figure out a different method in skinning DNN websites that makes the coded / designed Dot Net Nuke custom skin work even better and look even more original. With DNN we, the developers grow and so does Dot Net Nuke. It seems whether you’re searching for some DNN skin templates or you want to hire a firm to build your own custom skin, often times people feel that all DNN sites look the same. Well, I’ll I have to say to that is, open your creative mind, nearly anything is possible, a DNN site can look like any way you want it to. Skinning DNN websites is nothing more than stripping out all the content that is unique to each page and only using design elements and DotNetNuke Tags that will appear on every page. When done correctly, you can build your website using DNN the way it was meant to be built. While in my first few years working and designing DNN skins, I also felt that every site I was developing had a similar look and feel. Well those days are over, I have adapted as many others have to; opening my mind to making anything possible while designing a DNN skin and using the Dot Net Nuke Content Mangement System Framework the way it was constructed to be used.

Truly the best DNN skins are developed in such away, that the content dictates how the website looks; the skin is just the frame work and basic template for the guts that really create the overall look and feel. It’s crucial to design your skin using a core CSS file and XML file that control the key look and feel of site wide elements. More often than not, the designers / users that can’t control precisely how a DotNetNuke site looks, have either overlooked a CSS file that is stirring up their problems or have a lack there of, the necessary components in the core CSS file that are needed to precisely control a DNN sites layout, look and feel.

About a month ago, a very large client contacted us with a bitter taste in their mouth of DotNetNuke and their many frustrations over the past year with this CMS. Within our first conversation that day, I had quickly realized how poorly their DNN site was constructed. Within a matter of 3 hours after they had contacted me, I had already spoken with every key member involved in the company from the owner to CEO, to CIO, and to the uneducated DNN developer they had hired that left this bad taste in everyone’s mouth. To say the least, they were ecstatic with the information I had provided them, as they felt they were stuck in the “disaster” DNN world due to the custom module they paid for that ran their entire business. They soon realized the “disaster” was not DNN. The “disaster” was their developer. A month after the intital meeting, they had launched their new fully developed operational DNN site that they couldn’t be happier with. It was bringing them $400,000+ in revenue each month.

For the past 3 or so years, we have positioned ourselves as top DNN skin developers for small to enterprise level businesses all across the world. Probably 10% to 20% of the jobs we recieve for Dot Net Nuke cusotm skins, is a customer looking for someone who can fix where their previous DNN developer (aka skin expert) left off. Whether it’s because the two parties couldn’t communicate properly, the DotNetNuke developer just didn’t know enough about DNN to skin the customers current requests, or because they coded the skin in an incorrect and sloppy manner. It’s important to understand that DNN is very flexible and when developed in correctly, it’s an amazing open source Web Content Mangement System and complete web solution for many types of businesses big or small. Keep the Dotnetnuke community and Dotnetnuke CMS growing; develop wisely, correctly, and effieciently, and DNN will be here for a long time. Contact Us Today for a free quote and become part of the DotNetNuke revolution!