iFinity

A very useful feature of Google Analytics is the ability to track different urls for the same thing by including items such as campaign, source, medium, keyword and ad version.  This allows you to host links in different locations and then determine which is the most successful location, ad version, or combination.

This gives you extra information in your Analytics page, like this:



Above : Detailed Medium + Campaign information shown in Google Analytics from Url tracking codes

However, sometimes during the process of...

With the latest release of the Url Master module version, and the release of the Blog Module Friendly Url Provider, keen developers want to know about how they can create their own customised Url providers.

For a talented developer, there’s not much to it.  It’s just a case of implementing a derived version of a defined base class, and providing your own implementation of three main methods, one each for Url Rewriting, the generation of Friendly Urls and (optionally) any redirecting that must be done.

It’s possible to implement any combination of these, for example, to create a module that just does redirections or one that handles the translation of Friendly Urls back into a format for Url Rewriting.  Or you can implement all three.

Additionally, it’s...

With the release of Url Master 2.5, there is now the opportunity to publish custom Url providers for different DotNetNuke modules.

The first module provider to be released is the DotNetNuke Blog Module provider.

This provider allows an administrator to completely change the way that the standard DotNetNuke Blog Module Urls appear.

This is achieved by installing the provider as a DotNetNuke Extension, then configuring it through the new ‘Providers’ tab in the Url Master portal administration page.

What the provider does Fundamentally the provider inserts a layer between the Url that gets requested and the Blog Module itself, and another layer to the generation of Urls for display on the output Html page.  Of course, all existing DNN installations already have a Url Rewriting layer between the Urls and the underlying modules, but this has always been a closed box to the module developer. ...

I’m pleased to announce the release of the next version of the Url Master module.  This is a major step forward for the DotNetNuke platform in the way Urls can be managed.

The major feature in Url Master 2.5 is the inclusion of Custom Module Url Providers.

A Custom Module Provider is a compiled DotNetNuke Extension that works with the Url Master module to allow modules to use entirely unique and custom designed Url schemes.  This means that any module can completely break free of the imposed DotNetNuke Url pattern and use whatever format of Url the module developer wishes.

That’s right – not only do you no longer need the TabId of a DotNetNuke page in the Url, you don’t need the Page name (or path) either.  Not only do you not need the /default.aspx at the end of a Url, you don’t need to have any specific type of extension at all.

What’s more, you can mix and match module providers within your installation, and each provider can have different settings for each different portal in your...

The schedule for speakers for the DotNetNuke World conference has been released here: DotNetNuke World Schedule

If you’re coming along (and I assume you are!) then mark these sessions down in your diary – and come along and see your humble blogger give his opinions on the world, well, DNN World, that is.

Thursday 10th Nov, 3:30 pm to 4:20 pm

DotNetNuke on Azure Cloud Servers

Room : Palm 4

This will be all about providing the latest information on Azure integration with DotNetNuke, and is somewhat a follow up to the session I did last year.   You’ll be amazed at what a difference a year makes.



Friday 11th Nov, 9:30 am to 10:20 am

Tracking your Social Media Campaigns for Effectiveness

Room : Palm 4

Social Media is great and can be very effective.  The problem is working out which part is a waste of time, and which part is effective.  This session will be all about the strategies...

How to change your Telerik Html Editor in DotNetNuke to use a <p> block instead of <br> when you press the [enter] key.

I recently upgraded the ifinity.com.au site to DotNetNuke 6.0 in a moment of upgrade inspiration.    I won’t say the upgrade went completely smoothly because I had problems with the existing version of the DDR menu that was already in use on the site.  Those problems are yet to be fully resolved but it’s not likely to be a problem that everyone else will encounter.

Further teething issues have dribbled through in the days since the ugprade was done.  I have heavily invested in the use of jQuery and jQuery UI throughout the site, particularly so with the online licensing functions.   Of course, jQuery UI is now a first-class citizen within DotNetNuke and that has caused a few small issues.

Most of the problems thus far have been with the Licensing system, which is all a custom module that I built just for this site. 

The first thing I had to do was fix a bunch of javascript errors that were caused by having duplicate references to two different versions of the jQuery UI library.  For that,...