iFinity

This blog post brings together two threads of thought that I have been thinking about.   The first is related to my recent blog post Implementing jQuery and Javascript Libraries across DotNetNuke versions, and the second was a conversation with Scott Willhite at DotNetNuke World, who asked me why I hadn’t actually ever published anything in the DotNetNuke Forge despite writing lots of stuff.  I didn’t really have a satisfactory answer that didn’t involve using an excuse of inertia or procrastination.

My prior post on jQuery and Javascript implementation has been pretty widely read, and one of the comments on twitter was thus:



...

The big change for Url Master 2.5 was the inclusion of the ability to build custom module providers for generating module-specific Friendly Urls.  Part of this strategy was to develop a set of module providers for popular third-party modules.  This kicked off with the DotNetNuke Blog module provider.  

The next module provider to be developed is the News Articles Friendly Url Provider, which transforms the Urls generated and used by the Ventrian News Articles module.

The new provider is a plug-in...

DotNetNuke 6.0 brought jQuery UI directly into the framework as a ‘1st class’ DotNetNuke member.   It also allowed developers to request the DotNetNuke jQuery registration code instead of each developer independently including the library, which prevents multiple versions and the subsequent page errors this will create.  I have previously blogged about this in my post Using jQuery UI with DotNetNuke 5 and 6 in the same module.

With the release of DotNetNuke 6.1, the new Client Resource Management (aka imbibe) framework has been included.   This framework not only includes jQuery and jQuery UI in DotNetNuke, but it uses a client registration framework so that other libraries and Javascript files can be included in the correct order.  The best resource for this is Ian Robinson’s blog post : jQuery & jQuery UI in DotNetNuke 6.1 and 6.1.1.  ...

Something that quietly slipped past a lot of people at the start of November was the announcement from Google that was rolling out SSL Search for all logged-in Google users.

This can be broken down like this:

- SSL Search means that the search session is conducted over https

- logged-in Google users covers the universe of people who are logged into a google service, such as iGoogle, Google+, Gmail – plus a whole pile of others.

- SSL Searches do not provide the Keyword data in the referer value for a click-through from Google

This fact that SSL searches do not pass the search query data (ie, the keywords used) onto the site that is clicked on has a very large impact on Analytics packages, which collect that data and summarize it for analysis.

This means that data using any Analytics package (not just Google Analytics) will no longer provide keyword data for some Google searches.

...

Well, it’s a week since I returned from the whirlwind that was DotNetNuke World.  Already things are starting to slip back into normality from the head-spinning fury of activity that was the conference.

All I can say is that if you didn’t go, start pencilling in the date and the budget to go next year.

This was the first year that DotNetNuke had it’s own, stand-alone conference, one that wasn’t co-located with the bigger DevConnections conference.  It was also a change in location, from Las Vegas to Orlando.  These two changes made a very big difference to the feel of the conference.

Because it was only DotNetNuke people, it immediately felt more inclusive, more friendly and more focussed.  Because it was no longer in the cavernous halls of the DevConnections conference with what seems like a mile of walking to and from the hotel, it immediately felt more accessible.  And because there was *blink blink* outside areas to break out into, it gave everyone a chance to enjoy some warm Florida sunshine...

This blog post is a summary of my presentation at the DotNetNuke World 2011 conference held in Orlando, Florida.

This presentation was one that I have wanted to do for years, and my only issue was that I only had 50 minutes to present the life-cycle of a developer who has a great idea to receiving money for their sales. The session covered ideas, marketing, support, pricing, licensing, the new DotNetNuke store and much more.

This blog post is a summary of the presentation I did at the DotNetNuke World 2011 conference.

The topic was tracking social media campaigns for effectiveness – and the synopsis of the talk I gave was on how to use different metrics available from free tools, and how to combine those together in your own way to aggregate the data. Once that was done, using trends to identify which of your social media actions are effective in achieving your goals, and then double-down on the things that are working well

This post is a summary of the presentation I did at the DotNetNuke World 2011 conference in Orlando, Florida.

The sessions was centred around showing how to use the DotNetNuke Azure Accelerator which can be downloaded from Codeplex.

While doing some poking around on Google today I noticed an interesting change in the SERP result for this site. 

I tag all of the Blog posts with my own Tagger module which lists the tagged results out on a tag list page.  This is reached under a Url like:

http://www.ifinity.com.au/Explore_Tags/Tag/Redirect

The above Url lists out all the items on the site that have been tagged with ‘Redirect’.

Incidentally, the Tagger module was recently upgraded to a new version, which included popup tag editing and now can merge the tag results with the Core tagging modules.  This means you can use it as a tag cloud for core tags, or use it to add the custom tags as originally designed, or a blend of both.

Anyway, on this site it mostly is used to tag the blog entries, and then list them back out again when...

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