Have you ever wanted to have different styles for each page in your site? For example, in page A, the link's color is green while in page B is red, can that be done? The answer is a big yes, and it's a really simple one.

Just open the Page Settings and insert this code in the "Page Header Tags" textbox:

<!--

a:link { color:green }
a:hover { color:red }
//-->
</style>

Inside the <style></style> tag, insert your desired styles, and that's it!

You can see this in action in my Sirius - Free Skin For DotNetNuke portal. In the Tips & Tricks page, the link's color is green, which is different from every other page.

*Note: instead of configuring the styles inline, you can also link to a different style sheet; but IMO, that is an overkill!

-- 6/9/2008 8:05:00 AM --

Launch A Live Content Element Through Querystring

In this article, I'll describe how to launch a Live Content element through querystring. Actually this is already mentioned in Mandeeps.Com documentation, but I personally find it very useful and hope that you think so too.

Click "Read More" for detailed instructions.

*Note: Live Content is a commercial module from Mandeeps. It's one of the coolest modules I've ever seen in the DNN world.

-- 6/7/2008 7:48:00 PM --

Removing The Profile Visibility Option

In DNN, when a user edits his profile, there's an option that lets him control the visibility of some profile fields:

However, I find that this option, in many cases, is completely useless. For example, it doesn't have any effect in the "View Profile" page. It's also un-necessary when integrating with Effority's User Directory module. Therefore, I think that removing this option will improve the usability and coherence of a website.

In this article, I'll show how to hide this confusing option away, so that the final result looks like this:

---> A screenshot taken from Pijaja's Edit Profile page <----

*Note: although you can always have this done through the User Settings page, it'll only apply to the current portal. This hack helps you hide the option away by default for every portal under a single installation.

-- 6/7/2008 7:38:00 PM --

Redirecting all requests with "www" to non "www" ones and vice versa

Problem:

A problem you might encounter when managing a DotNetNuke portal is: You log in to http://domain.com , but you'll be logged out when accessing http://www.domain.com . Besides, this isn't good for SEO either, since the requests to your site will be divided into 2 parts: "www" and non "www" versions.

Solution:

Tom Kraak from SeaBlick.com proposed a wonderful solution to this problem WITHOUT touching IIS (there's a method using IIS though, also included in the article). Here's the link to the original post.

Hope this helps someone.

-- 6/7/2008 7:36:00 PM --