TheDNN

Some notes on the new release of TheDNN.Menu (1.8.0)

info@thednn.com — Sun, 23 Nov 2008 18:19:00 GMT

After a long period of time the next version of TheDNN.Menu is out including significant features and changes.

Here I am going to write a bit about the new features of TheDNN.Menu 1.8.0:

The most important feature in this release is the SEO compatibility. This as the most wanted feature over the past time which multiplies the power of the module in two different aspects. First it will let Search Engines crawl your website and understand the links. This feature is turned off by default, however you can enable it for a particular instance of menu using “Admin>TheDNN Menu Config>Menu Settings>(Select your menu instance)>Behavior>SEO Compatibility”. Next, by moving all the in-line CSS codes to external CSS files there is absolutely no CSS keywords in your page anymore. This will let Search Engines understand and extract the keywords of your website better than past and give it a proper rank. This change is constant and in-line CSS coding is not an option since 1.8.0.
Since the release of DotNetNuke 4.9.0 there was many reports on the issues you have had with the module. DotNetNuke 4.9.0 is now supported as well.
There were quite a few minor bugs around that are fixed. Thanks to our loyal clients.
The missing feature of being able to delete Looks and Skins is now added. So you don’t need to worry about building temporary and test skins on your portal. As long as the item is not in used you have the ability to delete it.

There are a few more changes as well:

The SkinObject and Module pack are now merged together. In past you had to extract the downloaded pack into two other packs and then install each of them. Now there is no need to extract the package anymore. All you need to do is to download the final pack and install it. The SkinObject will be installed along with the module.

Earlier, I mentioned that all the CSS codes has been moved to external CSS files instead of being implemented into your pages as it was used in previous versions. Despite the great result this is going to drive to your website, the downside of this significant and unpreventable action is that there might be minor changes needed to your current menu skins. Therefore it is normal if after upgrading to 1.8.0 you need to adjust your menu skin settings a bit. My strong advice for those who are going for an upgrade is to use a test environment and evaluate their menu skins first.

Something that took a long time to be prepared is the manual. Finally the manual for TheDNN.Menu.1.8.0 is released and you can have is downloaded from the Download page. TheDNN Group hopes that this document helps you getting to know the module better and don’t forget that your comments are really useful here, please let us have them.

TheDNN.SlideMenu is Released

info@thednn.com — Sat, 24 May 2008 18:42:00 GMT

The accordion module is finally out.

Many of you have asked for SlideMenu module so far. Here you are. :)

There are a few important points about SlideMenu:

Even though that this module is just released with version 1.0.0 but it contains all the improvements which has been implemented in Menu module so far. The Menu module is version 1.7.0 and we have had 7 releases till now. Therefore TheDNN.SlideMenu.1.0.0 has equal power comparing to TheDNN.Menu.1.7.5 (will be released tomorrow)
The navigation and the way working with SlideMenu is similar to TheDNN.Menu module.
Both TheDNN.SlideMenu and TheDNN.Menu will improve shoulder to shoulder and are integrated.
Because we understand that having both Menu and SlideMenu is essential for webmasters, therefore we are providing 50% discount if you have bought one of them before. This is a permanent discount.

After all, I want to tell you that we value your inputs and hear you. Please let us know your needs and comments about our modules.

TheDNN.Menu.1.7.0 Overview

info@thednn.com — Thu, 24 Apr 2008 14:02:00 GMT

This release is presenting two great features and an important change. This aimed to be a stable version and candidate for getting DotNetNuke Reviewed Logo.

Let me start by introducing the two new gold features:

XML Data Source

Until version 1.6.1 it was only possible to show the tabs available at DotNetNuke tabs including their position. The only thing you could do was to select another start node so that the children of that start node would become root items. In addition, you could include or exclude items and use the "Show Start Level Only" option to hide all the child items and display root items only (very useful for creating short cuts).

Beside all the pros available there, one could still feel a lack of customisability. The con was that you were not able to select items from different trees and create a new extra tab only for being in that particular instance of the menu module.

In TheDNN.Menu.1.7.0 you can create an XML file and assign it as your source of tabs to the menu instance. The structure of the XML file is very easy and has been described in the place where you can use it. Here I show you a sample of an XML file that can be used for the menu data source:

As you can see the structure is very easy to understand. You have title and url in tags named tab and you can have as many tabs as you want in serial or parallel.

The only thing you should note is that you can only use it with module and not the skin object.

Additional Menu Skins

There has been added a button in Control Center where you can use it once to install 16 extra menu skins. This is a new ability where gives more default skin choices.

But, why these skins are not installed while the module is being installed?
First of all, not everyone needs those skins and they will use resources of your website. Furthermore, we have plans to provide APIs for mass skin producers and this is a look into future as well.

Beside above two great features there has been a very important change in our module, and that's about the licensing system. Due to reported bugs with medium trust level we decided to completely change the licensing system. Therefore, please be aware that your license for older versions will not support 1.7.0.

Those who have purchased early versions and want to upgrade to 1.7.0 need to download their new license file. In order to have your new license we have created a Licensing Center application. As a result, all you need to do is:

Go to http://LicensingCenter.TheDNN.com
Click "License Files" tab
Enter your Invoice ID and download your new license file

Please note that the new license file will not work on early versions.

So, I guess it's enough for a kind of overview for the new release. Please remember that we value your inputs. ;)

Just a "Flash Forward"!

info@thednn.com — Sun, 20 Apr 2008 20:59:00 GMT

Although there is announced that the issue with Medium Trust level has been solved we have a few reports from our clients having problem running the module under Medium Trust level.

As based of our investigation, it looks like that the issue comes from our licensing system which works only under Full Trust level. So, we are now changing our current licensing system in order to fix the issue. This will be announced with V.1.7.0 of TheDNN.Menu.

Yes, V.1.7.0 is coming out with two more cool features. So, sit tight because the next post will be announcing this release with a brief description of the features.

Good news is that there will be a licensing center also available for our clients to have their licenses right after placing the order. So, there is no need to wait for your licenses to be issue and send over. More details come later along with the release of the TheDNN Licensing Center. ;)

TheDNN.Blog.HelloWorld();

info@thednn.com — Sun, 20 Apr 2008 16:16:00 GMT

Hello everybody. I am Jack, a staff of TheDNN Group. Here at the group we decided to start a blog regarding to our products and services.

I'll try to keep you updated about the events, and product news. Because DotNetNuke's announcement module doesn't support RSS, it might be difficult for you to come and look into what's happening here from time to time. Therefore, the first goal about starting this blog is somehow to replace it with the traditional announcement system.

Besides, it would be very helpful to gather your comments, and here is where it goes easy.