I am pleased to announce that DNN Platform 7.3.4 has been released. The 7.3.4 release is a stabilization release. DNN 7.3.4 is a smaller maintenance release than normal and is focused on addressing the most serious platform issues. It is expected that this will be the final platform release prior to DNN 7.4.0 which is expected to be released in January 2015. Once again the community has provided a number of significant fixes for this release. I look forward to increasing this level of participation coming in future releases.
You can find all of the issues resolved in this release in our issue tracker. Download 7.3.4 from the DotNetNuke Downloads page.

Major Highlights

• Fixed issue where site settings were not updating correctly in multi-language installations
• Fixed issue where partial site templates were not working correctly with child sites
• Fixed issue where links created in Telerik RadEditor were not correct
• Fixed issue where search results might be duplicated
• Fixed issue where user could not change default value for a profile property
• Fixed issue where a file uploaded from the web is not visible in the Host File Management
• Fixed issue where ControlBarController returned invalid JSON
• Fixed issue where you couldn't add a module in a spanish language site
• Fixed issue where a clustered index was missing from a search table
• Fixed issue where uploading an ICO file failed
• Fixed issue where HTML Editor Permissions were not working correctly
• Fixed issue where popups were not centered on the screen
• Fixed issue where popup iframe is not initialized correctly
• Fixed issue where AUM was not correctly handling 301 redirects
• Fixed issue where multiple region/country controls in a profile did not work correctly
• Added ability to save localized lists to resource file
• Added method to remove all subscriptions from a ContentItem

Security Issues

• None

Introduction

Recently there has been a lot of discussion in the community around DNN Spam registrations and methods and processes to prevent or fix the issues that are associated with them.  I've been debating on if/when I should actually write about this given that there is an Official DNN Software response on the issue, as well as many other community comments.  Well, when I had a server go down and guess what it was because of this very issue so I think its time to give my quick perspective and recommended action points for those of you that are running a DNN site.  These recommendations apply for ALL DNN versions!

Update Registration Mode Setting

If possible, set your registration mode to "none" if you don't need public registration.  This is a great first defense.  If this isn't possible, then go with the next best step and that is to create a custom registration page.  If you do this, though make sure that you follow the instructions in the next step.

Optional: Add IIS Request Filtering

One of the recommended "stop gap" items that DNN Corporation recommends for those that cannot set registration to "none" is to set a filter in IIS for request filtering.  I STRONGLY recommend this solution and am rolling this out to ALL DNN sites that I manage or have any control over that need to allow user registration.  This will prevent the most basic backdoor used by these scripters which should at least help limit things a bit.

Post Change Investigation & Resolution

This is the key, the above changes are quick & easy, but it is the investigation that is key.  I'm writing this post because of the investigation and resolution that I had to do tonight while on vacation.  I had a server that went down, with a clients database that grew from 45mb to almost 1gb in 7 days, had a user count grow from 2 users to 197,000 users in that same 7 day period.  All of this happened silently, without stressing server resources, without setting off any DDOS alerts or anything.  How did it become an issue today?  The site owner tried to make a change and then it fell on its face.

So, given that this can be a silent threat to your site, what do you need to look for, and what actions can you take to fix?  Lets look at these next.

Do you have impacted Users?

If you are lucky, your site will not have any impacted users and you can stop here.  However, if you go to "Admin" -> "User Accounts" and see that you have 50,000 users when you should only have 10 you have some work to do.  This is the fastest way to look at things and identify what is going on.  If you have rogue users you will need to do two things to truly 'clean' your installation from these user accounts.

Delete the User Accounts

The first step in resolution is to get rid of the users that are impacting the site.  How you accomplish this is going to vary a bit.  If you have 5, 10, 20 SPAM users, just manually use the DNN delete features, but make sure to note the User Id value for each user.  If you have a lot of users, for example in my case more than 100K users to remove, you are going to want to investigate a scripting solution.

I will not post direct SQL here as you NEED to be a user with proper SQL knowledge to do this, but you can do this VERY fast and very clean within DNN.  Simply set all of the users that you need to remove to "Deleted" in the database, then use the "Remove Deleted Users."  Now, this process of having DNN remove the users might need to be repeated as there is a 30 second timeout on DNN database queries.  In my case it took 10 attempts to remove all.

Delete the Folders & Re-Sync Files/Folders

This is one area that is not often remembered by administrators with fake accounts.  Each user that is created in more current versions of DNN have a folder created for them inside of the users folder within DNN.  You will want ot go in and delete all of these folders from the filesystem.  Then once that is completed you will want to go to "Admin" -> "File Manager" and sync the filesystem.  This is imperative as more entries in the folders and permissions table will slow down areas of the site that interact with these tables.

Conclusion

We need to see what the final fix is for this issue, but in the meantime we need to be vigilant and keep our own sites as protected as possible.  Given the nature of this issue I am being a bit vague in recommendations as the exact solution isn't going to be the same for all users and sites.

Now you'll be able to add Google maps to posts. Post might have the primary post map, and with tokens you'll be able to include a limiteless quantity of maps to content articles. Maps may be very easily created and edited by way of the in-built Map editor.

Within this blog I'll clarify How you can insert new google maps into DotNetNuke 7.3. Google has up-to-date Google maps to new UI and features.

So will start with Google maps very first.

Click the Google applications on right top facet of one's browser. Open up Google maps appplication.

You will be landed to New Google maps. Type your address or location in the search box. For instance i have added Madame Tussaud Newyork.

Once your location is targeted on google maps.Click on setting at the right bottom side of the map and select share and embed maps.

A modal popup will look on the display with Share hyperlink and Embed map alternative. By this you are able to possess the link in the map to provide to any hyperlinks if required else we can select to embed the map into your site or application. Also you'll be able to shorten the URL if necessary .

Given that we need to embed google maps into DNN we are going to choose Embed maps alternative. After you click on embed maps option you'll have a smaller sized see of maps you've selected i.e in my scenario Madame Tussauds The big apple with ratings, reviews, bigger map choice and obtain directions. You can even bookmark if necessary.

OK once you have got map on Embed maps. Now you can choose the size of the map required based on your requirement. Google offers small, medium, large and custom size.

We can change the size of the maps by using custom size.Google maps also provides option to preview your custom size by clicking on preview option.A new window will be popped out for preview.

For now we will be using Medium as our map size. Will select medium size and copy the iframe provided.

Once iframe is copied will now login to our DNN (DotnetNuke). Add username and password and login to DNN.

Once DNN is logged in. To place our Google maps on our site we need to add a HTML module to our site. This can be added  by navigating to Modules > Add New Module > Selecting Common from the Drop down.

Once common option is selected from drop down options will be narrowed to HTML. Drag the HTML module to your selected pane in my case i am adding module to Content Panel.

Now we have added HTML module to our Content panel. We need to edit content inside our HTML module. This can be completed by clicking on pencil icon existing on the HTML module. In the event you dont have pencil icon navigate to Edit page choice on proper leading corner in the DNN control panel. After pencil icon is clicked click on on edit content.

Once you select Edit Content. A modal popup will appear with all editing option. Initally the editr will be in Design mode change the mode to HTML. This can done just by clicking on HTML option just below the editor.

Once you selected HTML mode. Paste the iframe we copied from Google maps to the HTML editor in DNN. After pasting the iframe to DNN editor save the module by clicking on save button.

Thats it Google maps will be embeded on your DNN page in a following way.

Hope you liked my tutorial.

DotNetNuke is a widely adopted open source platform for building web sites and web applications with a Content Management System build on .NET. WebMatrix is a free tool that allows you to create, customize, and publish webpages. It gives a number of different ways that you can create websites. One of the features is providing existing open sources applications such as DotNetNuke, as well as WordPress, Joomla, DotNetNuke or Umbraco. In this tutorial, you will see how quick and easy it is to get your DotNetNuke application up and running! And show how to install, configure and publish a DotNetNuke application with WebMatrix.
If you do not already have WebMatrix, it can be downloaded for free at www.microsoft.com/web/webmatrix.
When you launch WebMatrix you will see several options on how to create a new application. To create a DotNetNuke application, select “App Gallery.”

We will now choose the “DotNetNuke Community Edition” icon to install the application. You can give your application a name or keep the default name.

You will be prompted to select a database. Select “SQL Server” and make sure the “Windows Integrated Authentication” radio button is selected and click Next.

You will be prompted to install DotNetNuke. To do this you must click the “I Accept” button.

Now we wait while DotNetNuke is installed. This make take up to a couple minutes.

Once the installation is complete we will get a confirmation.

Clicking the “OK” button will take us to our WebMatrix workspace with the DotNetNuke application loaded.

To configure our DotNetNuke application, we will use the Installation Wizard. To run our installation wizard, click the “Run” button on the Menu Ribbon. Note: make sure you run the root folder of the application. Running our application will open the DotNetNuke Installation Wizard. Here we will have three different options for installation: custom, typical and auto. For this article, we will use the typical installation.

To successfully install our DotNetNuke application, we must first pass a permissions check. The installation wizard will notify you if you passed the check or not.

After we pass the permissions check, we must enter our database information. In this example we’ll use a SQL Server 2005/2008 (Express) File.

Once the database connection is created, the installation wizard will install the database for you. The installation of the database can take quite a few minutes.

Once the database installation is complete, a confirmation message will appear at the bottom of the window. The “next” button will once again be enabled. We must click “next” in order to continue with the installation wizard.

We now will have to create a Host account. Fill in the form and hit the “next” button. It is a good idea to write this information down.

Once your installation is complete you will be able to access your portal and log in.

In order to customize our application, we now need to login to our site as an admin. You should have been automatically logged in when your site was created. Once you are logged in as an admin you will have access to more features that allow you to customize your page. A tool bar will be present at the top of the screen.
We can add a new page to our site by adding the required information of name, what template, and where to insert the page to our application.
Mouse over the Pages link at the top and click the “Add” link which will show us a form where we can fill out information about our page.

After filling out the information, select “Add Page” so that we are directed to where we can add content to the page. Do so by clicking on the “Edit Content” link. This will cause an edit box to appear where you can add text and images with styling options that code the HTML for you (if you are in the “design” tab).

Once we are done customizing our site, we can publish our application. There are several companies that are offering free WebMatrix hosting. You can find this information under the Publish icon on the ribbon or by clicking the link on your WebMatrix workspace.

And We created our DotNetNuke application.

This is a single that threw me for a long time, nevertheless the remedy is actually quite simple. Easy sufficient that i really don't understand why there is not much more documentation on it.

Here’s the scenario: You've got a module with two, or maybe more, achievable interfaces depending on the web page the module is additional to. The view handle features a blank important area and you cannot have copy crucial fields, blank or in any other case. How can you power the non-blank module control to point out around the page with out further coding?

The answer: make use of the module definitions.

Here’s how.

A number of assumptions very first:

You’ve developed a custom made DotNetNuke module.
You have at the very least two module controls in that module.
You've got a DotNetNuke set up to check on as well as the custom module is installed.

Now stick to these actions to show multiple view controls.

1. Log in as the host user, open the extensions page, and click the edit icon to edit your module
   
   

   

2. Your module already has a default definition that typically includes a view, edit and settings control.  The setup looks something like the picture below.  (Note: In editing this image I accidentally shortened the source paths.  The format should be DesktopModules/My Custom Module/View.ascx)
   
   

   

3. Click the “Add Definition” link next the “Select Definition” drop down.
   
   

   

4. On the new screen fill in the information to create the new definition and click “Create Definition”.  In this case I’m calling it “Definition 2″, but you’ll want to make your definition names descriptive, or whatever meets your naming convention needs.
   
   

   

5. Now you’ll have a fresh new module definition to fill out just like the default definition.
   
   

   

6. You can now add new module controls to the definition.  Click the “Add Module Control” link and fill out the form as a new View control by leaving the “Key” field blank.  Fill in the title field, select the source and leave the Type as “View”.
   
   

   

   
   
7. Update the definition and navigate to the web page in which you would like to incorporate the module. Incorporate the module towards the webpage. In the event you had already additional the module you’ll require to delete it and incorporate it once again or else DotNetNuke will not operate the code to add all of the see controls. Once you incorporate the module you ought to see each check out handle you produced a definition for look around the page as being a individual module occasion. In the event you do not, return and verify you accomplished the steps properly.
8. At this time whatever check out controls you really don't want to look on the web page, merely delete that instance from the module.
   

The Visual Studio Starter Kit enables you to create a compiled DotNetNuke module that can be much more compact, more quickly, and hide your supply code from prying eyes. The subsequent instructions can get you started and well in your approach to creating compiled DotNetNuke Modules.

1. Download the Starter Kit
2. Open Visual Studio  and create a new project (File -> New Project)
   
   

   

   From the dialogue follow these steps
   
   
   • Select Web from the Installed Templates. I use of VB.Net, but they are available in C# too.
   • Pick DotNetNuke Compile Module from your Project Type list.
   • Enter your Module Name
   • Enter the path for your DotNetNuke installation. Your project will be installed within the current set up within the DesktopModules folder and also the dll will likely be place in the bin folder.
   • Click OK
3. Visual Studio will load up the venture within the Solution Explorer and open the Documentation.html in the editor. You’re not however ready to set up the module so don’t keep to the DotNetNuke documentation but.
4. In the Solution Explorer right click on My Project and select Open.
   
   

   

5. Within the Application tab delete the entry in Root Namespace except if this is your only module, otherwise you will not be sharing code with other modules. I have a undertaking that spans numerous modules and i want them all inside the identical identify space. So, I delete the basis Namespace entry to ensure that I am able to put within the appropriate namespace from the code driving. (Edit regarding Root Namespace; in C# you do not need to clear the namespace, but in VB.Net you are doing).
   
   

   

6. Switch towards the Compile tab. Verify the Build output path and make sure its pointing towards the proper bin folder. Now simply click the Advance Compile Option on the button of the tab. Around the dialogue make certain the target framework is correct. You’ll see the environment on the base of the dialogue. At this point the dialogue will immediately near.
7. Repeat step 4 (open the project properties) then go to step 8
8. Switch to the References tab.  You should see a reference to DotNetNuke.Library version 0.0.0.0.  Remove it.
   
   

   

9. Nonetheless around the References tab, now click the Add button. Inside the Add Reference dialogue switch to the Browse tab and navigate for the DotNetNuke set up bin folder. Choose the DotNetNuke.dll, DotNetNuke.Web.dll, as well as the Telerik.Web.UI.dll. Should you do not hold the Telerik.Web.UI.dll then you definitely should not be making use of those controls and you also will not want the dll. Click Okay. These references are necessary to obtain access to the DotNetNuke methods and properties. In any other case you are code powering will be crammed with inexperienced and blue underlines, missing references, and, oh yeah, it won’t compile. Sort of defeats the aim, proper?
   
   

   

   
   
   Intellisense; this step is optional, but if you want Intellisense you’ll want to do this.  Switch to the Web tab. Under Servers select the “Use Local IIS Web server” option.  Change the Project URL to the full URL of your project (eg http://{domain}/DesktopModules/{project folder}).  Check “Override application root URL” and set it to the domain of your DotNetNuke install (eg http://{domain})
10. Save the Project Properties and close it.
11. Inside the Solution Explorer increase the Components folder and open up the ModuleNameController.vb (or .cs) file. Check the Namespace declaration and you’ll see that it states “YourCompany”. Change this to your customized namespace identifier and after that do the identical in each of the code powering documents. You will also need to change it inside the .ascx files because they’ll be reference the namespace inside the handle declaration at the best of the webpage.
12. At this point you can Build your project and you will see the new dll in your DotNetNuke install bin folder.
13. Now follow the instructions in the documentation.html to install the module in DotNetNuke.  Once the module is installed you don’t really need the documentation folder, or it’s files.  I usually delete it.
    
    

Obtaining up and operating with all the templates is really pretty straightforward, but you must stick to some really certain measures, not subsequent the measures tends to make it hard for anyone else in order to assist you as you can configure issues any number of ways that might cause difficulties.

Configuring your Development Atmosphere

This really is 1 from the most significant steps from the procedure, the templates are configured to operate in a site You'll find a couple of assets for placing up your environment. The crucial thing for your new release of the templates is you need to have DotNetNuke 7.3 operating at dnndev.me, unless of course needless to say you modify the templates your self, but that's outside of the scope of this weblog post.

Putting in the Templates

Installation in the templates is pretty simple, you'll find numerous techniques to complete this, select one in the a few choices beneath and carry out the actions outlined for the option you decide on. You simply have to do one of those choices, not all three.

1. Put in utilizing the Tools\Extensions and Updates menu in Visible Studio 2012
   
   • Mouse more than the Tool menu
   • Click on Extensions and Updates
   • Search for DotNetNuke
   • Select the Put in button to the DotNetNuke Project Templates option
2. Install manually by downloading the VSIX file from the online gallery
   
   • Pay a visit to the Visual Studio Gallery - DotNetNuke Project Templates page
   • Download the VSIX file via the Obtain website link.
   • Double click the downloaded file to install the templates.
3. Set up manually by downloading from Codeplex
   
   • Down load the VSIX file from Codeplex
   • Updated - Right Click the downloaded VSIX and choose Properties
   • Click the UNBLOCK button before proceeding
   • Double click the downloaded file to install the templates.

Making your Visual Studio Project

As soon as you have put in the templates, you can set up a project based on the templates. To do so you need to stick to the steps under

1. Set up Visual Studio 2012 (you need to have this done presently)
2. Install the undertaking templates as instructed above
3. Setup your DotNetNuke Advancement Environment as instructed over
4. Operate Visual Studio 2012 as an Administrator (correct click on the shortcut to do so)
5. File -> New Project
6. Choose possibly C# or VB.Net from your Languages segment of the new Project dialog
7. Pick the DotNetNuke Folder under your preferred language (C# or Visual Basic)
8. Choose possibly DotNetNuke C# Compiled Module, DotNetNuke VB.Net Compiled Module, DotNetNuke 7 C# DAL2 Compiled Module or DotNetNuke 7 VB.Net DAL2 Compiled Module for the project template.
9. For the new project creation screen using the following settings
   
   • Title: ModuleName (something distinctive here, instance MyModule)
   • Place: c:\websites\dnndev.me\desktopmodules\ (this assumes you set up your improvement surroundings as instructed in Step 3)
   • Solution: Create new solution (this option might not be exhibited, that's okay)
   • Create directory for solution : Unchecked (this may trigger route issues if checked, the templates presume the SLN is inside the same folder since the project file)
   • Add to source control: Unchecked (I typically get my undertaking operating before incorporating it to supply control)
10. Click Ok
11. In certain cases Visual Studio will change the DesktopModules folder in into a Digital Listing, this will cause problems with your DNNDEV.me environment, load IIS Supervisor (start>run>INETMGR) and take away the Virtual Directory if it appears as a single there.

Installing your Module in Improvement

Once you create your project in Visual Studio 2012 the module will exist within the c:\websites\dnndev.me\desktopmodules\MyModule folder, but it is not technically installed and registered with DotNetNuke. To complete that you need to execute the follow steps.

1. Develop your Project in DEBUG mode.
2. Modify to Release mode and build again.
3. Login to your improvement website within a browser, using a HOST/SuperUser account.
4. Navigate for the Host/Extensions web page
5. Pick the Install Extension Wizard option
6. Simply click Choose File
7. Browse to your c:\websites\dnndev.me\desktopmodules\MyModule\Install\ choose either the INSTALL or SOURCE package to upload.
8. Go through the measures for the installation wizard (if the module fails to install, attempt closing Visual Studio very first, then set up the module)
9. Location your module on a page (I usually produce a fresh webpage for each module in my development environment for tests reasons).

Setting up your Module in Production

To install your module in production you'll keep to the same actions as installing it inside your improvement environment, other than you will nearly Never utilize the Source package of the module in creation, it just is not essential.

What’s Subsequent?

So I lastly received the 7.0 (7.3) templates out the door, what is subsequent? Reworking the DNNTaskManager module which i created a module advancement tutorial for back in 2011. The program is to actually rewrite that module from the ground up utilizing DNN seven.0, in a few distinct iterations. 1) Utilizing the unique DAL design in DotNetNuke, 2) Using the new DAL2 template, 3) Utilizing ContentItems in DotNetNuke 7. Keep tuned to my weblogs to learn more as those tutorials are produced.

Certainly one of the commonest queries which i get by way of the community forums on this website, or via e-mail is "How does one get your websites to operate so fast". Although not excellent, my web sites normally operate somewhat more quickly than your typical DotNetNuke 7.3 websites. Formerly I have stored the exact particulars of my changes to myself, nevertheless, with a litle encouragement from the neighborhood I've chose to share the full context of the changes that i make into a default DotNetNuke set up to acquire better baseline performance, as well as added products that i do to aid when i actually want that "boost".

Overview

To begin with I want to begin out by declaring that a great deal in the details that's shown listed here could be located in previous website postings. Posts this sort of as DotNetNuke Host Options Explained, DotNetNuke Scheduler Explained, DotNetNuke Overall performance Options Defined, and straightforward DotNetNuke Performance Enhancements. Are good beginning factors for a few of the element driving my recommended adjustments.

The subsequent changes are merely the configurations that i have found for being the very best "baseline" configurations. Consideration is required in regards to the web site setup, update frequency, traffic, hosting environment and users to ensure that you have the correct set up for your particular atmosphere. I'll talk about the options section by segment, merely noting the modifications which can be created. Remember to reference the specific "Detail" doc for more information.

DISCLAIMER: Adhere to these suggestions as a manual only, I am not responsible for any results of employing these adjustments.

Host -> Host Options Changes
The first place I pay a visit to may be the Host Options page. There are a selection of key updates and adjustments required on this segment. Again, only changes are noted right here.

Appearance
In this segment I uncheck the "Show Copyright Credits" box

Advanced -> Authentication Settings
Within this segment I uncheck "Enabled" for almost any provider that will not be utilized in the portal, normally the LiveId and OpenId companies

Advanced -> Performance Settings
On this area I change the "Module Caching Method" to Memory. the "Performance Setting" to HeavyCaching. As well as the "Compression Setting" to GZip Compression.

Advanced -> Other Options
In this section I modify the "Scheduler Mode" to Timer. I enable the "Event Log Buffer" and i disable the "Auto-Sync File System" alternative

They are the commonest Host Options adjustments which i total. Based within the website I'll make a couple of other little edits.

Host -> Scheduler Changes
The largest alter that i make right here would be to modify the "SearchEngineScheduler" task to run normally as soon as every 12/24 several hours. This reduces a big load around the server.

Other Modifications
From a DotNetNuke configuration alter which is all that I modify. Overall these adjustments typically outcome in extremely noticable efficiency advancements, but often times it just isn't adequate to maintain the web sites operating as smooth as possible. So according to the specific situation I have numerous other things which i function with.

Normal Purging of Occasion Log
As a lot of people which have utilized DotNetNuke have identified the EventLog table could become a very troublesome hinderance within the performance facet of a web site. Enabling the Event Log Buffer helps reduce the consequences of the huge EventLog, nonetheless, the most effective policy is always to thoroughly clean the EventLog on a normal foundation.

I try this one of two methods. By myself sites I have an SSIS package deal inside of SQL Server that truncates the desk each 24 hrs. On customer web sites I make use of my Scheduled SQL Employment module to keep a seven working day rolling historical past of the EventLog information. The key here is the fact that we must keep the occasion log tiny.

Skin Choice and Menu Provider
The next item of thought is actually a multi-part thought. I target on finding CSS primarily based pores and skin layouts that use 3rd party menu parts this sort of as Telerik and Css NavMenu. With a straightforward pores and skin modify to sites I've seen webpage load occasions which have decreased by more than 50%.

Discovering an excellent designer that creates well laid-out skins with 3rd get together menu suppliers is a crucial overall performance enhancement, a minimum of in the page. I've NOT benchmarked these numbers although because DNN 4.six.2, so the core menu company might have much better performance.

Compression/Caching Modules
Like a last stage, if I actually need to get the most performance out of a website I will often lean towards Snapsis PageBlaster as being a good alternative. I at present use PageBlaster on this website only and also have had really excellent luck with it, though when configuring the module you have to be cautious to test all functionality very first. This was another change that after applied I seen really noticeable efficiency advancements.

With all the introduction of the DDRMenu to DotNetNuke, we've experienced much more manage above what is rendered from the menu. This has authorized for a a lot more semantic menu and custom made styling for easy menus to mega menus. There are numerous methods to create the template that the DDR makes use of but we'll be using the token primarily based templating because it is quite easy.

Menu Template (Bootstrap Nav)

I copied the easy folder from your Gravity pores and skin that will come with DNN 7, which incorporates a manifest file “menudef.xml” and the “SimpleToken.txt” file. I updated the SimpleToken.txt file as follows:
Notice: this isn’t a tutorial on DDRMenu, just how to apply Bootstrap.

<ul class="nav nav-pills">
    [*>NODE]
    </ul>
    [>NODE]
        <li class="[?NODE]dropdown [/?][?SELECTED]active[/?]">
        [?ENABLED]
            <a href="[=URL]">[=TEXT] [?NODE]<b class="caret"></b>[/?]</a>
        [?ELSE]
            <a href="#">[=TEXT] [?NODE]<b class="caret"></b>[/?]</a>
        [/?]
        [?NODE]
            <ul class="dropdown-menu">
            [*>NODE]
            </ul>
        [/?]
        </li>
    [/>]

1. Add the classes nav and nav-pills to the outer ul. Individually, I favor the simplicity in the Simple tablets nav that bootstrap gives. This appears to be the easiest to override with my own custom design and style as I have a tendency to use more flat UI’s in my style.
2. Include the category “dropdown” for the list merchandise if it's youngsters using the [?NODE] examination.
3. Add the category “active” for the listing product whether it is selected utilizing the [?SELECTED] examination.
4. Add a caret to the merchandise if it's a baby item.

Up coming, we are able to include the HTML and pores and skin object within the pores and skin as follows:

Logo and Menu pores and skin objects (Bootstrap Navbar)

<div class="navbar">
        <div class="navbar-inner">
            <span class="brand">
                <dnn:LOGO runat="server" id="dnnLOGO" />
            </span><!--/Logo-->
            <dnn:MENU MenuStyle="Simple" runat="server"></dnn:MENU>
        </div><!-- END navbar-inner -->
    </div><!-- END navbar -->

1. add link with class “btn” and btn-navbar”. Also, requires markup for collapse. You are able to use either JavaScript or information attributes.
2. Wrap dnn:MENU pores and skin item using a div using the adhering to class
   “nav-collapse” and “collapse” - this permits the menu to break down at smaller display screen sizes
   “pull-right” to drift the menu to the correct side, if you so desire.

Note: making use of this process will disable a menu merchandise which has children. In order that this is a click to open up motion. This can be to make things function much better for contact units.

The Simple Way to Install DotNetNuke

DotNetNuke is a Web-content management platform for those who use the Microsoft ASP.NET framework. Based on your company needs, whatever version of DNN you choose, it will be a significant cost saving venture over other options. Installing DotNetNuke is not a task well-suited for beginners to this sort of website framework. If you are familiar with websites, databases, and ASP.NET, you can use these instructions to learn how to install DotNetNuke.

Check the DotNetNuke installation requirements before getting started. To install DotNetNuke, you need a database with either Microsoft SQL Server 2005/2008 or SQL Express. If you have an older version of DotNetNuke 5.2 or earlier, you can use SQL Server 2000. You should also have a Microsoft IIS (Internet Information Services) with version 5 or higher, and the Microsoft .NET 3.5 SP1 framework. This service pack is available through the Windows Update feature.

Download the latest version of DotNetNuke to your computer, and unzip the file.

Use the FTP software of your choice to connect to your website, and upload the installation files into the directory of your choice. If necessary, create the directory where you want to install DotNetNuke on your server.

Select the folder where DotNetNuke is located. Click "Properties," choose the "Security" tab, and add the necessary user permissions. Use either the local ASP.NET service (for Windows 2000 and XP) or the local Network Service account (for Windows 2003, Vista, 2008, or 7). You should have permission to modify the folder.

• Open the IIS server console. Go to "Start" > "Run" > INETMGR. Click on the "websites" node, and select the "Default website" node.
• Right click on the DotNetNuke folder. Click "Convert to Application." If this option is not available, select "Properties" and add the application.

Install DotNetNuke with SQL Express.

• Open your web browser, and go to: http://yoursite.com/dotnetnuke.
• Walk through the installation wizard as presented on the screen. The database information should already be configured, and you should not need to change it.
• Look for the default login information for the "host" and "admin" users, which is shown when installation is complete.
• Log in immediately, and change the passwords to protect against hacking.

Install DotNetNuke with SQL Server 2005/2008 for your database server.

• Open SQL Management Studio, and connect to your database server.
• Walk through the installation wizard as presented on the screen.
• Create a new database by expanding the server node, then the databases node, and filling in necessary values for all the database properties.
• Set up the SQL user and security account, and choose the appropriate integrated-security or user-security setting under the "server/security" node.
• Open your web browser, and go to: http://yoursite.com/dotnetnuke.
• Walk through the installation wizard as presented on the screen. Choose SQL 2000/2005/2008, and follow the security steps according to the option chosen in the previous steps. Test the database connection.
• Finish the installation wizard, and look for the default login information for the "host" and "admin" users.
• Log in, and immediately change the passwords for those accounts to protect against a hack.

Best and Cheap DotNetNuke Hosting Provider

Are you looking for best and cheap DotNetNuke Hosting Provider? ASPHostPortal is the answer. ASPHostPortal.com is a windows-based hosting service provider. ASPHostPortal.com offers the most reliable and stable DotNetNuke 7.3 web hosting infrastructure on the net with great features, fast and secure servers. Our hosting can be done via USA, Amsterdams or Singapore based server. Depending on your requirements, we can scale so we can deliver the right service for the right price. All of our windows hosting plan supports DotNetNuke 7.3 and you can install DotNetNuke 7.3 with just one click.