http://www.dotnetnuke.com/Resources/Forums/forumid/112/threadid/451288/scope/posts.aspx

Of particular interest on the site is a new module or ours soon to be released to the DotNetNuke Community called Mushroom Video Module.

The module will feed Youtube Play Lists from youtube.com directly into your site in an easy to manage and easy to use video feed.

The end result of the feeds looks like this:

http://www.networkyou.org/Network/GlobalVillage.aspx

With the video feeds being selected directly from a play list selector button that referenced a YouTube account name.

The module also uses the template system developed by InteractiveWebs for the display system that allows simple to load templates to be customized to the users requirements.

An example of the module with multiple feeds onto a single page is this one: http://www.networkyou.org/Network/Professionals/VideoTopics.aspx

We will be releasing the module to the public in the next few weeks. We would love to hear any comments!

Today we updated some code in our Contact Details module for DotNetNuke.

The module makes it easy to add your contact details to a page in DNN.

There is a map control function that uses Bing Maps that can be seen in the demo here: http://www.interactivewebs.com/contactdetails/Demo.aspx

We have updated the module today to support the use of SSL or https connections to the page that contains the module.

How we did this

So here are the two ways to add the Bing Ajax control to your page in HTTP or HTTPS:

HTTP:

<script src=”http://ecn.dev.virtualearth.net/mapcontrol/mapcontrol.ashx?v=6.3” type="text/javascript"></script>

HTTPS:

<script src=”https://ecn.dev.virtualearth.net/mapcontrol/mapcontrol.ashx?v=6.3&s=1” type="text/javascript"></script>

Now on the HTTPS version notice I changed the URL to start with HTTPS, this is what pulls from the secure site over at the good Bing folks. Also notice I added the “s” parameter and set it to 1, default is 0, this tells the Bing API to get the image tiles for the map from HTTPS.

Why? you ask.

Well it seems that the API determines what protocol to use for JavaScript and other parts from the document.location.protocol, however when it comes to the map tiles it looks to a global setting that is set based on the parameter being passed.

Today we have added this feature to the DotNetNuke Advanced Login Module.

User Name Omission

Normally DotNetNuke requires a user name to be entered at registration. The Advanced Login Module will automatically create a DNN user name at registration time, even if the token for User Name is not included in the registration form. This way you can allow users to register with an email address and no user name, while in the background the Advanced Login Module handles the user name for you.

How It Works

If omitted from the registration form, the user name will be taken from the email address.

david@domain.com for example will generate a user name using all data from before the @ symbol.

david@domain.com = david as the user name.

If david is already taken as a user name, then david-01 or david-02 etc. will be used automatically.

This keeps the username familiar to users should it ever be provided to them, yet keeps the registration process as simple as possible.

The module is available as a Free DNN Module trial on our site.

To correct this, we have created two new templates that are designed specifically to work with the DarkKnight skin in DotNetNuke.

Called:

• DarkKnight-Small
• DarkKnight-Large

They produce the following results…

With the Large template being the content on the left, and the bottom right showing the content of the small template.

This makes the module perfect for use with DotNetNuke 6x our of the box.

How to Set the Templates

The templates are selected through the normal RSS Template Tab in the module.

1. Select Load Template Button

2. Select the appropriate template and press the select button.

That will load the new templates and be ready to use on your site.

Advanced Login module for DotNetNuke works with DotNetNuke 4x, 5x and now 6x.

However because DotNetNuke 6x has some popup effect by default with the login button it interferes with the Advanced Login Module popup mode.

Solution

To fix this issue, the solution is relatively easy.

After selecting “Popup" from the Advanced Login Basic Settings Edit the skin object login and register as follows.

Default Settings

Update to:

Login

#dnn_Login,#dnn_LOGIN1_loginLink

Register

#dnn_USER1_registerLink

Save Tab Changes

Update to Templates

Then we need to make a small mod to the templates. After Selecting the Templates tab, click on Custom Script.

And modify the script to:

jQuery(document).ready(function(){
    /*
     add any custom initialization logic here,
    */
       jQuery("#dnn_LOGIN1_loginLink").attr("onclick","");
       jQuery("#dnn_USER1_registerLink").attr("onclick","");

})
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;
}

Note: We added two new lines highlighted in yellow.

Save Tab Changes and you should be done. With the default skin in DNN 6.0.1, now the advanced login popup mode should work fine. Look at the Advanced Login Module for more assistance with configuring the module with different skins.

InteractiveWebs DotNetNuke Modules require a license to be activates on each sub domain from which the module is accessed.

The license is per sub domain, and NOT for each instance of DotNetNuke.

A sub domain example is:

1. www.domain.com
2. dev1.domain.com
3. domain.com

In the case of domain.com and www.domain.com, these are considered as one single license. EVERY other sub domain needs it’s own license.

If you activate a module on dev.domain.com then browse to the same module using another sub domain (like dev2.domain.com) the module will not be activate with the new sub domain in the browser URL.

Trial

Each module will automatically enter into a 100% functional TRIAL mode the first time you access the module with any particular sub domain.

The trial period is automatically set from the date you first visit the module with any particular sub domain.

Example

If you access dev1.domain.com the module will start it’s trial period from today, and may expire if you don’t activate.

If you then use another sub domain like dev2.domain.com the module will start a new trial and you will continue to be able to access the module on that dev2.domain.com sub domain.

Note: All the settings and modifications you make to any module in trial WILL be preserved and waiting for you once you activate the module license. So if your trial expires on your development sub domain, you can simply activate the module in it’s final www.domain.com location when you are ready to go live.

Before You Activate

We recommend that if you need to configure and test (development site) before going live, that you do that on a development sub domain (like dev.domain.com), IN TRIAL MODE.

From that dev.domain.com, Setup the module, test and be sure things are working. Don’t be concerned if you get things just right, and the trial time expires. Because as soon as you access the module page on a new sub domain, it will go back into trial, and be available fro activation.

All your module settings and customizations will carry over to the new sub domain when you access it. So in this example, if you are ready to go live with www.domain.com you can access the module page with that sub domain, and extend the trial, or activate the module.

For this reason we always suggest that you only activate your module on www.domain.com as your final public URL of your website.

To Activate Your Module

Select the Licensing Dropdown Menu Item from the module Menu:

The module will tell you about the Module Name, Version Installed, sub domain you are on, and trial days remaining.

If you have not purchased a License yet, you can click the Buy Now icon and purchase a license from our site.

Note: Check that the sub domain shown in the module is the final correct sub domain you wish your license to be active on:

Click: Request License Activation

Fill in the details requested, including the store you purchase from and the email address that you used with your purchase.

Note: The email address must be the one you have on file. With SnowCovered, it is apparently possible to have more than one address on file. The address we need is the one that is in the purchase order confirmation data sent during purchase. This is the accounts primary e-mail address.

Wrong License E-mail Address

If we are unable to match the email address against a valid license activation, we return the error:

We suggest that you verify the email address used for purchase and try again with the correct address. You can also monitor your License Management on our site by logging in with the email address that you try to activate with.

Correct License E-mail Address

With the correct details, you will receive a message like this:

Managing Licenses

You can monitor your licenses and activations by visiting our License Management page here.

Ensuring that you login to our site using the e-mail address that the license was purchased with.

Module Support

We provide several Support services for our modules.

1. Where necessary our modules come with extensive manuals (like our bulkemailer module).
2. Each Module has it’s own pages on our website. Visit the module website by clicking on the correct module from this list: http://www.interactivewebs.com/DotNetNukeModules.aspx

Then use the support menu to find module specific support. This will include KB Articles, Support Forums, Blog Posts.

Although the default DNN login is much improved, the advanced login module offers a range of especially useful feature that can greatly improve the users experience.

http://www.interactivewebs.com/advancedlogin/DNNLoginModule.aspx

Today we released a version of Word Editor that is ready and tested on DotNetNuke 06.00.00 release.

The popular Word Editor module allows users to edit the content of HTML on a DotNetNuke website using Microsoft Word 2007 or later.

If you have not seen the module, check out the website here:

http://www.interactivewebs.com/dnnwordeditor/AboutDNNWordEditor.aspx

Or the online demo here: http://demo.interactivewebs.com.au/dnnwordeditor_demo/dnnwordeditor_demo.htm

Today we released an update to the Automatic Backlink Module for DotNetNuke.

Details of the update are available here: http://www.interactivewebs.com/automaticlinkbuilder/Support/VersionHistory.aspx

But include improvements on the way site monitoring is handled and the way the module works with the known GZIP issues.

An example of the module can be seen here: http://www.interactivewebs.com/Admin/DotNetNukeWebsites.aspx?&action=add

where you can add your site for back linking.

Today we have released a new version of our Users Online gadget is getting ready for our iPhone app release that will support this module.

Today we have released a new version of the DotNetNuke Users Online Gadget module that allows you to monitor your website from:

• Windows Gadget
• Mac Widget
• Google Gadget

Todays update can be seen here: http://www.interactivewebs.com/usersonline/Support/VersionHistory.aspx

and is getting the module ready for the pending release of our iPhone app that will allow you to connect and monitor your site directly on your iPhone.

After Installing the DNN Module, you add it to a page on your DotNetNuke website as you would any other module.

The page can be visible to the public or visible to only administrators. Either way the module will function fine.

Once on the site the module will display something like this.

Steps to Using the Gadget Widget App on your site

1. Download the appropriate Gadget, Widget or App by selecting the “Click do Download” link at the top of the module.

2. Install the Gadget to your local website.

3. Enter the configuration of the Gadget / Widget as you would any others on your local computer.

4. In the Settings for the Gadget / Widget enter a Title to use to identify the site you are connecting to. The title will display in the top of the gadget.

5. Then enter the URL for your site, remembering to use the child portal name if you are on a child portal. For Example:

Parent Portal: http://www.interactivewebs.com

Child Portal: http://www.interactivewebs.com/usersonline

(Where UsersOnline is the Child Portal name)

6. Enter a refresh cycle for the gadget / widget to run off to your site and retrieve new data. (Recommended 300 seconds).

OK and you are done!

Note:

Clicking on the Users name in the Gadget will deliver you to the sites user profile page.

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:

www.interactivewebs.com/blog

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.

An Example

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.

Look and Feel

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.

Linking to the Full Content

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.

Caching

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

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.

DotNetNuke Solution

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.

How Modules Use DNN version of jQuery or their Own version

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.

Best Resolution

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.)

Other Possible Problems

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:

http://ajax.googleapis.com/ajax/libs/jquery/1/jquery.min.js

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.

What is the Take Home Message?

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 end result

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.

slidedown-export

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.

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.

Basic Settings Tab

1. Mode = Popup

2. Show Profile as Popup

Giving a Basic Settings tab looking like this:

Template Tab

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.

jQuery Settings

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.

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.

Basic Settings Tab

1. Show Both – Display Mode

2. Slide Down – Mode

We saved Tab and out demo page looks like this in the back end.

Template Tab

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.

DotNetNuke 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.

Setup a Page for Login

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.

1. Login to your site with Host or Admin permissions.

2. Navigate to the page you wish to add a form to.

3. From the DNN module menu select FEEDBACK DESIGNER and the Pane Location.

4. Select ADD to add the module to the seelcted pane.

5. You will see a warning message advising that the module has yet to be configured. This message will only be seen one time.

6. From the Complete Feedback Designer menu on the module, select CONFIGURE MODULE.

7. You are now presented with the Module Menu. From her select the options you wish to edit by clicking the corresponding CLICK HERE.

The problem has always been the fragmentation of web technologies and browsers. Browser brands, versions, libraries, server technologies, uptake of new technologies like Silverlight etc has all been issues for us.

It’s one thing for us to develop a great solution, only to find that others struggle to have it implemented correctly. Silverlight is a classic example of this. Versions of SL and operating systems like mac vs pc really make a difference.

What we came up with

JQuery was the solution. Now that DotNetNuke had the core library built into the CMS, we are able to use it and find that most people have little or no trouble with it. We even managed to upgrade or template management system to use the new JQuery based UI. This makes the loading of the template management pages very fast.

All of the module can be Downloaded Free from our DNN Module Download page here.

Automatic Link Builder 55.01.13
Automatically create and mange backlinks into and out of your websites to help improve SEO effectiveness of your site.

Tell My Friend 45.05.33
Add a "Tell A Friend" jQuery popup module to your site to allow visitors to spread the word of your great website. Add a "Tell A Friend" link to every page of your site in minutes.

Subscriptions Module 45.02.02
Subscriptions and advanced PayPal auto recurring subscriptions module with tax zones.

Bulk Emailer Download 45.05.96
Bulk Email for DNN with reliable campaign management and advanced tracking features, link tracking, recurring campaign and opt-in module.

Analytics Report 45.01.17
Display your Google Analytics data directly to your DotNetNuke website.

The module can be downloaded from our site in a trial that works 100%. You can test and play with the module, then purchase from Snowcovered our our site if you wish to purchase.

The module allows for a fantastic user login and registration experience, with complete control over all aspects of the look and feel and the effectiveness.

We have completely redone the UI for the module:

This helps make the complicated custom options really easy to understand, and helps users with the different modes of the module.

Additionally we have added new features that can be viewed here: http://interactivewebs.com.au/advancedlogin/Support/VersionHistory.aspx

Some of the new features include:

1. Custom Role Registration during Signup
2. Additional Questions / Answers during password retrieval
3. Custom form messages for during signup and login
4. Detection of duplication of user accounts during signup
5. UI Improvements mentioned above
6. Updates to the extensive user manual

Download the trial module here.

This can effect our DotNetNuke Module – Microsoft Word Editor, as it uses the Microsoft Office Add-in feature of office.

The cause of the problem lays in Microsoft (again) that have decided to make Word (and other office Add-ins) mark a plugin as “Disabled” if it is ever involved in a slow response or crash.

Good concept to stop plugins crashing word, but how they do it is so unobvious it catches many people out. The plugins are added to a “Disabled” basket, and will never again be activated unless moved from that basket. Even if the add-in is uninstalled and re-installed.

To fix the problem you need to remove the add-in from this list of disabled items in your office application.

It does not escape comment that Microsoft Word remains the only application I know of that has a crash recovery system built into it. Rather than fix the problems that cause it to crash, they built a system to recover after crashes.

Since Word 2000, you can take an INDEX and regenerate it, then fast scroll on the newly created index to crash the entire application. 10 Years of development, and all I can see is tweaks around the edges. No wonder the company is on a massive down hill slide! “Microsoft – Taking the fun out of computing”.

Some of you may be aware that Microsoft recently released a new feature in Outlook 2010 called the Social Connector. It allows you to feed data from social sites like LinkedIn and Facebook, into your Outlook.

When someone sends you an email, or you open a contact or calendar item, the social connector will use the email address of the outlook data to find related social information and feed it into your site.

With the new DNN module – Outlook Social Connector for DotNetNuke we are feeding data from your DNN website directly to Outlook.

This makes it incredibly easy to see relate a website users activity on your site to an email received by that user.

We are yet to document the module and create a supporting website. As soon as we do, we will be releasing the module. Stay tuned.

DotNetNuke Automatic
Link Builder Module

Automatically Manage Links to and from your website with this powerful DNN Module.

Others linking to your website is a powerful way to improve Google (and other search engine) rankings of your site. This DNN Module will help you to automatically:

• Request and Engage Members of your site
• Accept their back link requests.
• Monitor that a Reciprocal Link to your site was created.
• Validate the Back Link to your Site
• Allow you to Approve or Reject the Link with a single click
• Automatically have Google Index the sites that link to your site.
• Continue to monitor the backlink remains in existence
• Continue to submit to Google the back linked sites for indexing

Best of all, it is easy to use and configure, with simple options for complex tasks. Read More Below.

Build Google Ranking

Build the Google ranking of your site by having others contribute back links to you with an automatic process that tracks and manages the entire process.

jQuery powered

The backend controls are powered by powerful jQuery controls and interface that makes for easy to use management of the module..

Simple Control Panel

As with all our products, we work hard to keep our interface simple. Again with this DNN module, we have made the control of options as simple as can be.

CSS Design Control

Use CSS to control the look and feel of the module within your website. Every aspect of the look and feel can be easily managed as templates.

Automated Control

The module will run in a fully automated mode controlled by the DNN scheduler process to perform a range of automated tasks.

Custom Messages

Send out custom e-mail messages to your customers based on custom templates that are managed directly in the module settings.

Role based Messaging

You can select a website security role or roles to automatically invite members to contribute links to your site. Email messages will be sent automatically to the users in that role inviting them to contribute.

Automatic Management

The processes of the module are entirely automated and use the existing engine that DotNetNuke runs on. DNN Scheduler.

Screen Captures:

How it works.

1. You configure Email Templates that invite and engage members of your website to link from your website to theirs, and return the privilege.

2. You define roles in your site that members of which will receive an email invitation to contribute links.

3. Users arrive at your site and fill in a link from your site to theirs

4. The module will email the user who submitted their link and advise that in order for the link to be listed on our site, we must be able to validate a back link from their site to ours. This is where you would include instructions about how they may best achieve that.

5. The module will automatically generate an icon of the submitted website.

6. The module will spend a number of days checking the link submitted, searching for a back link to your site.

7. If a back link is found, the module will send you (that administrator) and email message allowing you to view and approve or reject the listing.

8. If approved, then another email is sent to the link submitter advising them of the approval, and the link is listed on your site.

9. If the link is not found, or you reject the link, then an email to the submitter is sent advising them of this too.

10. Approved links are sent to Google for indexing to ensure that Google is notified of the backlink to your site.

11. The existence of the back link is periodically checked, and the listing removed if the backlink is not found, and email notification to the link owner is regenerated.

12. Link management remains in your hands if desired.

13. CSS and Templates can be managed

Details:

Specification

Description

Database

SQL Server 2005, 2008 and Express

DNN Versions

The module requires DNN 5.5.0 or Later.

Download Package

PA Install Files for supported DNN Versions

Version History

Here

Source Code

Source code is not available for the module.

Updates

Free Unlimited Updates in accordance with our update policy Here

The reality is that for over a year we have been playing with various technologies and trying to work out what would be best for user management UI. We tried Ajax, Silverlight, ripped images with direct .net code, java and we believe we have it right using some jQuery controls.

Check out our update and see what you think. Remember all our DNN modules are free to trial.

DNN Tell My Friend Module

The DNN Tell My Friend (Tell A Friend) is an advanced DotNetNuke module that allows you to easily as a module to one or many pages of your DNN website.

Now with Advanced Jquery code for improved reliability with other Ajax modules and skins!

The custom DotNetNuke Module displays a link as either a URL or image button that when clicked, will open a light box style of effect to allow the browser of your site to tell their friends about your page or site..

This advanced DotNetNuke module is easy to setup and adds a powerful network marketing aspect to your website.

We have released an update of our popular Microsoft Pivot DotNetNuke Module.

Mine your DotNetNuke user accounts to spot trends in your accounts and signup history. Microsoft "Pivot" allows you to organize and display data like never before.

The new technology recently released by Microsoft Labs is allowing the visualization of data that would otherwise be difficult to explore.

Take a look at the Ted Talk Video below to understand this technology, and imagine how you could use it with your DotNetNuke membership data.

There is nothing else that can sort and arrange data like Microsoft Pivot!

This module is exciting as it allows you to easily launch your profile data as a pivot within minutes.

here is nothing else that can sort and arrange data like Microsoft Pivot!

We were inspired by the recent video shown on the ted.com website by Gary Flake.

View the Microsoft Pivot Video First

When uploading an mht or mhtml file to Bulk Emailer moduel for DotNetNuke. You receive a message that looks like this:

The File C:\Inetpub\XXXXXXX\httpdocs\Portals\0\filename.mht Is A Restricted File Type. Valid File Types Include ( *. swf, *.jpg, *.jpeg, *.jpe, *.gif, *.bmp, *.png, *.doc, *.docx, *.xls, *.xlsx, *.ppt, *.pptx, *.pdf, *.txt, *.xml, *.xsl, *.xsd, *.css, *.zip, *.template, *.csv, *.htmtemplate ). Please Contact Your Hosting Provider If You Need To Upload A File Type Which Is Not Supported.

Solution

1. Login to your DotNetNuke website as a host.

2. Navigate to the HOST / Host Settings page – Other Settings

3. Add ‘,mht,mhtml’ (without the ”) into the Allowable File Extensions.

4. Click Update and you are done.

DotNetNuke only allows certain file types to be uploaded by default. You need to allow DNN to accept the Microsoft MHT or MHTML file type if you plan on using it with Bulk Emailer.

Check out the demo and read more about the DNN module here: http://www.interactivewebs.com/analyticsreport

We have an example of the DNN module running on our analytics report site here.

DotNetNuke (DNN) Analytics Report Module

Google Analytics Report Module allows you to display your Google Analytics Graphs in a custom module on your DNN website.

This allows you to use the Google Analytics free service with your client’s websites, and deliver the results directly to the client without them leaving the DNN platform. This effectively replaces the DNN site log data with a neat flash colour graph of the Analytics Report data.

Now you can have advanced analytics data in your site and have it appear to be part of the DotNetNuke Module Platform that you deliver to clients.

This is another Custom Module for DotNetNuke by InteractiveWebs.