*** NEW VERSION ***

I've just finished modifying my XM Radio Gadget for Windows Vista Sidebar.  Works with the new XM/SIRIUS player. Use your XM Radio Online account to listen right from your sidebar.

Recently, I was experimenting with LightWindow in a DotNetNuke portal.  The scripts work great in Firefox, but were giving me fits in IE7.  I checked out the LightWindo forums and discovered the fix was setting the DOCTYPE to:

So, from there my quandry was how to set the DOCTYPE in a DNN Portal.  Well, In 4.4 and above, you are able to define the xhtml mode as a part of the skin by adding an xml file that that is named [SKINNAME].doctype.xml. Within this xml file you should declare one node SkinDocType. Then, within a CDATA tag, you add the doctype declaration to be used for this skin.  For example, if your page uses Portal.ascx as the skin, you would create Portal.doctype.xml in the same directory.  Be careful though, changing the DOCTYPE might have nasty side effects on some skins.  The xml file should have the following content:

I've developed several custom DNN modules, but none required more than the single view, edit and settings controls that are created with the starter kit.  Well for my current project, I needed two edit controls.  Creating the controls is easy if you follow any of the instructions you can find by googling "create custom dnn module".   

 What I wanted though was similar to the Events Project module that had multiple edit controls on the dropdown and on the links (bottom left corner of most module containers).  Copying the Starter Kit example proved easy to add a second edit control, but it only showed on the Module Menu DropDown, not in the list of action links at the bottom of the module.

Here's the code I started with:

This code did not add the second action item "EditSlides" to the Action link list at the bottom of the page.  After lotsss of trial and error and looking at other modules (plus reviewing the docs at http://www.dotnetnuke.com/), I finally reached the answer, putting the correct ModuleActionType - AddContent in the third parameter of AddAction.  When I switched the code to:

Then I got both the action items on the link list at the bottom of the module.  Also note that the first parameter of Localization.GetString was change to a string that coorelates to a StringName.Text entry in the resource file.  For example, EditSlides.Text = "Edit Slides" in the resource file.

And the results...two edit controls in the link list at the bottom of the module control.

Cheers...Don

Today, my designer handed me a fixed height design for a web page and was adamant that a text area have a vertical scroll bar.  I hate scroll embedded scroll bars but I sought out a solution and found a rather elegant one.