We “Eat our Own Dog food”; as the saying goes (user our own software), and use the module on our own site in many locations. Have a look at these pages, much of the content is from our blog site here:
http://www.interactivewebs.com/feedbackdesigner/Support/HelpandSupport.aspx
http://www.interactivewebs.com/mushroom-image/Support/HelpandSupport.aspx
Check out the links and the way the Mushroom Lite Module for DotNetNuke works.
Mushroom Lite Module for DotNetNuke is a module developed to bring rich content in an 
RSS feed directly into your DNN website.
We created the module to fill a particular need we have that would allow us to bring a WordPress blog to DNN, but it could be any sort of blog, or any RSS feed with images and text.
Our blog is at: http://www.interactivewebs.com/blog
We use WordPress to power the blog, because it is extremely powerful as blog technology, and far superior to many other blog technologies available.
The blog allows RSS feeds of almost every item listing, either by cloud tag, or category. It is one of the powerful features of WordPress. If you click on a Category such as iPhone, you receive this web view: http://www.interactivewebs.com/blog/index.php/category/apple-mac/
and if you add /feed/ to the end of that URL, you will be given the same content in an RSS feed.
http://www.interactivewebs.com/blog/index.php/category/apple-mac/feed/
Shown in Internet Explorer
The same content can then be fed into the InteractiveWebs Mushroom Lite DotNetNuke Module using the same URL as above.
Giving a great result on page. Note that the module is automatically pulling
or
So in this way, you can bring your blog content in the form of an RSS feed directly to the page of your DotNetNuke website, and display it in style.
Best of all, the module allows you to customize the layout using CSS, jQuery and a template.
Loading Effect
With Loading Effect also controlled by template, allowing you to select a number of effects.
The last tab on the module shows the installed version, and if there are any updates available past the version installed.
With the images pulled from you RSS feeds, you can set the image display size.
Set the number of characters pulled from the feed source:
with the automatic truncation of the content stream.
The module allows for the reader of your page to click on the content and view the original stream in several styles:
With handy information sharing links built into the popup:
for sharing your posts.
There are also options that allows for sorting the feed:
To allow you to use the module and it’s feeds in different ways. For example we use the post on this page.
http://www.interactivewebs.com/mushroom-lite/Support/HelpandSupport.aspx
to provide a help and support for one of our other modules. The posts in this page were done with the most relevant to least, so the content we want at the top of the page remains there.
An important part of performance is that the module does not hit an RSS stream each time the page loads. We have provided for this with server site caching, controlled within the module.
Allowing you to define how frequently the module reloads the RSS stream with new content.
For more information and demonstration, see our site here:
http://www.interactivewebs.com/mushroom-lite/MushroomLite.aspx
DotNetNuke can use jQuery to enable popup style and image rotator effects. These are great and a big improvements on technologies like flash. However it is not hard to find two separately coded jQuery modules that can cause conflicts when used on the same page as each other.
The reason in most cases is that modules can be hard coded to use their own version of jQuery. (Think of jQuery as a plugin that is required for the code to load onto the web page).
The library that powers jQuery is often updated to include new features. Earlier version of DotNetNuke did not have any ability to load jQuery or reference it as “part” of the core of DNN.
So for any module written for early DNN versions, the library plugin for jQuery needed to be included or referenced to an online source like the free Google jQuery reference.
If two module are on the same page and calling different versions of jQuery into play, it is likely that one of the modules will conflict and fail to work correctly. Often it will be the more advanced or later built module that fails.
The solution to this is to built a common core library into the core of DotNetNuke, and allow modules and other code to reference this single source when calling on the jQuery library for any reason.
DotNetNuke have included jQuery as an option in the host settings, to allow it to be loaded from there.
They run a release version of the jQuery library that is presumably updated with releases of DotNetNuke. The last version of DotNetNuke 5x shows this.
Modules can either call this library, or use their own library.
Well developed code or modules will usually have a setting that allows you to reference the HOST DNN version of jQuery, or call into play the version that shipped with the module.
On our modules, we use a tab setting that looks like this:
If the “Load jQuery” is ticked, the module will use the jQuery library that is shipped with the module.
If the option is not ticked, the module will use the DotNetNuke included version of jQuery.
When conflicts occur, the best way to resolve it is to ensure that both modules are referencing the exact same jQuery library version. The easy way to do this is to ensure that both modules are NOT using their own version, or in our case “Load JQuery” is NOT CHECKED. 
And, ensure that any other modules are also not referencing their own version of jQuery but are looking to the hosted jQuery. (Talk to the module developer on how to do this.)
1. One of the modules may require a feature that is more advanced than the the hosted jQuery version. In this case, a later jQuery library will need to be referenced. To allow this to be done, DotNetNuke have allowed you to reference a URL for another version of jQuery.
For example, in our Mushroom Image module for DotNetNuke, the rotator effect requires a later version of jQuery than the last version of DotNetNuke 5x references. 1.4.4. To set a later version, you simply find an online resource like this Google hosted jQuery library:
And enter that URL into your HOST jQuery settings.
2. Another issue is that there may be a conflict in the jQuery script used to call the module actions. We have included the ability to customize the script used to reduce conflict.
Naturally this is an option for advanced users, and not all modules have this feature.
When a conflict occurs, there is usually no “developer” at fault, but rather an incompatibility between the ways that the jQuery is being called. Don’t assume that the last module installed is to blame.
In most cases the conflicts can be resolved using the steps outlined above. This assumes that the modules installed have similar flexibility as we do in our modules.
We had a situation that clearly shows the use of the DotNetNuke Advanced Login Custom Script template, and how it can be used to deliver expected results.
The client wanted to use a custom search function that enabled search, twitter and Facebook into the top area of their skin.
The issue was, that when the this would cause some errors with the way that the search would display on top of the Advanced Login Module slide down effect that was set to run on the site.
The solution to this turned out to be a great example of how the “Custom Script” option from within the module, can be used to deliver a custom experience that takes into account other custom features of the skin or site.
So in this case we needed to move the Search, twitter, and Facebook information into the same layer as the slide down effect. We then changed some CSS styles to make the alignment of the item sit in the correct place on the skin, and not move to the right when the skin was on a wise display.
or
The custom script ended up looking like this:
jQuery(document).ready(function(){
jQuery(“#open”).click(function(){
jQuery(“div#adv_slidedown_panel”).slideDown(“slow”);
jQuery(“.search_style”).css(‘display’,'none’);
});
// Collapse Panel
jQuery(“#iwebs-close”).click(function(){
jQuery(“div#adv_slidedown_panel”).slideUp(“slow”);
jQuery(“.search_style”).css(‘display’,'block’);
});
// Switch buttons from “Log In | Register” to “Close Panel” on click
jQuery(“#toggle a”).click(function () {
jQuery(“#toggle a”).toggle();
});jQuery(“#dnn_dnnLOGIN_cmdLogin”).css(“display”,”none”);
jQuery(“#dnn_dnnUSER_cmdRegister”).css(“display”,”none”);if(jQuery(“.wsc_login”).length>0){
jQuery(“.wsc_login”).css(“visibility”,”hidden”);
}jQuery(“.search_style”).appendTo(jQuery(“.tab”));
jQuery(“.search_style”).css(‘margin-top’,’10px’);var w=jQuery(“.search_style”).offset().left- jQuery(“#s_wrap_main”).offset().left-jQuery(“#s_wrap_main”).width()+jQuery(“.search_style”).width();
if(w>0){
jQuery(“.search_style”).css(‘margin-right’,w+’px’);
}})
function custom_validate_login(){
/*
add any custom login form validation logic here,
return true if pass validation
*/
return true;
}
function custom_validate_registration(){
/*
add any custom registration form validation logic here,
return true if pass validation
*/
return true;
}
The end result being that the skin, search and advanced login module slide down effect works well together.
Google Picasa has the ability to enter a description for an image. That description text is usually an explanation of what the image is about.
We have the ability to access this description text of images using the token: ${item.description} within the template.
To make this easy, we have added a second template to the templates within this module, using the same name but with “Desc” in the name.
Where The – Dec versions of the templates like the Light box-Desc will display the description text.
The templates remain editable as usual, to those of you who are skilled with HTML, CSS etc. We just thought it would be best to include these templates to simplify the process.
Today we have released a new version of DotNetNuke Advanced Login Module that supports the upload of an image file as part of the user registration process. The image file or [Photo] token, takes advantage of the profile item in later releases of DNN that allow a user to attach an image of themselves during registration.
The feature is only available to DotNetNuke 5x releases, and is yet another good reason to update from DotNetNuke 4x.
Under the Advanced Login Module, select Templates Tab
Then “Registration Form Template” and expand the Tokens Available.
Navigate to the “Profile Field” and click to see the list of available tokens.
The new [Photo] token is available in that list.
When used in code to that looks something like this
<div class="advRegister_box"><br>
<table cellspacing="0" cellpadding="3" border="0">
<tbody>
</tbody>
<tbody>
<tr>
<td><span class="advLogin_LabelText">Username</span></td>
<td>[username|class=advLogin_text|tabindex=3]</td>
</tr>
<tr>
<td style="padding-top: 5px;"><span class="advLogin_LabelText">Email </span></td>
<td style="padding-top: 5px;">[email|class=advLogin_text|tabindex=4]</td>
</tr>
<tr>
<td style="padding-top: 5px;"><span class="advLogin_LabelText">Password </span></td>
<td style="padding-top: 5px;">[password|class=advLogin_text|tabindex=5]</td>
</tr>
<tr>
<td width="200px" style="padding-top: 5px;"><span class="advRegister_LabelText">First Name </span></td>
<td style="padding-top: 5px;">[FirstName|class=advLogin_text|tabindex=6]</td>
</tr>
<tr>
<td style="padding-top: 5px;"><span class="advRegister_LabelText">Last Name </span></td>
<td style="padding-top: 5px;">[LastName|class=advLogin_text|tabindex=7]</td>
</tr>
<tr>
<td style="padding-top: 5px;"><span class="advRegister_LabelText">Photo </span></td>
<td style="padding-top: 5px;">[Photo|class=advLogin_text|tabindex=8]</td>
</tr>
<tr>
<td align="right" style="padding-top: 10px;" colspan="2">[register_button|class=advLogin_Button|style=float: right;] [register_login_button|class=advLogin_Button|style=float: right;]</td>
</tr>
</tbody>
<tbody>
</tbody>
</table>
</div>
You will get a result that looks like this.
That will feed the photo file into the Profile Item “Photo” with DataType “Image”
Apple has released the the official video of the Keynote Speech from the June 6 2011 opening event.
To watch the video browse to the Apple Events (Apple Special Event) Website and Watch the streaming video from the WWDC 2011 keynote.
An example of the DotNetNuke user login via way of jQuery popup effect can be seen here.
The example shows two button images defined that when pressed will give the pop-up template effect shown here.
Popup of Login
Popup of Register
The configuration of this mode is really easy to manage.
1. Mode = Popup
2. Show Profile as Popup
Giving a Basic Settings tab looking like this:
We selected the Template-gray.
Look and Feel
We loaded some .png images for the Login and Register Buttons, and set the profile form width and height.
We left as default.
That was it. This will place the module into a Pop-Up mode, allowing dotnetnuke users to register on your website with a jQuery style of popup effect.
The DotNetNuke Advanced Login Module offers a New Slide Down Effect as seen on the Demo pages on the dnn module website here. Or see our DotNetNuke forum post here.
Some interesting and easy to use effects that are template driven and display content with the dropdown effect replacing the normal login and registration skin objects on your site.
The configuration of this mode takes only seconds to configure. With these quick Options.
1. Show Both – Display Mode
2. Slide Down – Mode
We saved Tab and out demo page looks like this in the back end.
1. Load Template
Select Grey – then press the Select Button
Save Tab Changes and we are done.
The template page looks like this:
Giving a great resulting page that looks like this:
We also put up tow examples of the Slide Down DotNetNuke login effect that are done in RED and BLUE.
DotNetNuke Slide Down Demo – Grey
DotNetNuke Slide Down Demo – Blue
DotNetNuke Slide Down Demo – Red
All are using the same skin template, but with different CSS colours defined, and different slide down templates in the Advanced Login Module.
How to Configure DotNetNuke Websites to use DotNetNuke Advanced Login ModuleDotNetNuke had the ability to configure a custom page to be used as the login page on your website. This page does not need to appear in your menu structure and the login process can effectively be made to use the Advanced Module in a seamless way to the default DNN login process.
1. Create a New Page in your DNN Website using the normal Add Page Method: 
2. On that new page, uncheck the menu item for Show in Menu, and make the page viewable by all users or unauthenticated users:
This ensures that people who are not logged into your website have the permissions to view the login page. 
3. Add the DNN Advanced Login Module to the web page, and format the page as desired. Remember too that you can have content that is visible in different states. i.e. Users that are not logged in can see modules and content set to “unauthenticated” but cannot see content for Authenticated users until they have logged in. We use this to our advantage on our DotNetNuke Module Download Page, by providing instructions to people about login before they are logged in, but after they are authenticated and logged in those instructions are no longer displayed.
4. Configure the module into the mode you wish to use for login. Options like logging in with email address in place of user name etc. This is an example we use for the login settings to our site:
5. To set the page you have just created as the default site login page, go to the Admin / Site Settings / Advanced Settings / Page Management, and select the page you have just created as the login page for the site, and set the Home Page as the page you wish to display by default after users have logged into your site:
The end result is that when someone clicks on the “Login” menu option in your DNN skin they will be directed to the login page of your website. Once authenticated the user will be directed to the Home Page, unless they were looking for a members only URL when they hit your website. In that case the login process will deliver the user to the original place they were attempting to reach.
They say the best technology is the technology you don’t notice. This is most definitely true for a lot of truly revolutionary technologies. Take the fuel management system on the Airbus A380. Constantly moving and controlling distribution of fuels around multiple systems, taking into account best distribution for weight and balance, safety, economy, possible errors and general automation of management.
A truly great example of technology that is unnoticed, and just goes about doing what it was designed to do well.
Before installing the update, you have to realise that Windows 7 is actually the in house patched (fixed up) version of the off shore experiment that went so terribly wrong for Microsoft. Windows Vista. With almost no new features in Windows 7, you could really call it the true SP1 to that junk they called Vista.
That in effect makes this SP1 release for Windows 7, a SP2 for Vista. In other words, they are really just fixing stuff they have either since found or did not have time to fix from the initial release.
Take a look at their Windows 7 Service Pack 1 “What’s included in Windows 7 Service Pack 1(sp1)” website, and you begin to get the idea.
See the feature list?
Me either… They list exactly nothing. Nothing is included in SP1 for Windows 7. They have no features, no additions and no reason to update.
One general reference only to “Reliability” and “HDMI Audio Services”. We already know that “reliability” is a word that has been banned from being used in conjunction with Microsoft products. But HDMI Audio…
So you already can see where I am going with this. There are no features, there is nothing to draw you into this release. So if you are finding that your Windows 7 install has yet to fall apart and is otherwise working like a well service patched version of Vista. Then leave it alone!
If you are installing from scratch, then best practice would probably have you install SP1. I could not argue otherwise.
Be Warned.
Like all things Microsoft, there are plenty who wish they have not installed SP1. Some of the problems include:
Colour problems
Failure to install – "Installation was not successful" DS_S_SUCCESS(0×0)
Windows 7 SP1 Fails to Install ‘0x800f0826′
Windows 7 Service Pack 1 fails to install with 0x800f0a13
Fatal Error C000009A applying update operation [number] of [number]
Windows 7 Service Pack 1 – Installation Failure ERROR_ACCESS_DENIED(0×80070005)
Just to name a few issues.
Microsoft are so aware of these problems, that they have released an official tool to help you prevent your system from bugging you to install SP1. They call it the Windows Service Pack Blocker Tool Kit. Along with the Windows Live Writer, it is probably the best tool released by Microsoft since Steve became the boss there (Developers Developers Developers).
Time is money, and my time is valuable. I’m leaving this one alone, as I simply don’t trust Microsoft any more. They are time bandits and service packs with no features and loads of problems, smell terribly like a time bandit about to suck up another day or two of my life in Microsoft Hell.
I am looking forward to Tomorrows WWDC 2011 Key Note Speech. It is ironic that I once was this excited about the Microsoft releases. I wonder what “magical” new things Apple have installed for me this year?
Today we updated out profile at Codeplex http://www.codeplex.com/site/users/view/InteractiveWebs
mostly so that we could slam a review up for the latest dotnetnuke 5.6.2 release. The review points out that the release is not one of the worst releases of dotnetnuke, but it is buggy and caused us some problems. We are quite disappointed that this is the last 5x release, and hold little hope about the initial releases of DotNetNuke 6x.
Shame for all the hype and spin that dnn corporation have been putting on themselves that they are so happy to release such junk.
