What is New in DotNetNuke 7.4.2?

The latest version of DotNetNuke is 7.4.2. This version has been released at October 6th 2015. This release is maintenance release, bug fixes and support for incremental updates.

SECURITY ISSUES

This release resolves the following two security issues:

• 2015-06 (Low) Potential XSS issue when using tabs dialog
• 2015-07 (Medium) Users are getting registered even though User Registration is set to None

What started out as a relatively small maintenance release has turned into one of their largest maintenance releases ever. They spent a lot of time working to resolve a number of password management and multi-language issues along with a few performance enhancements. In total, they ran well over 5000 manual and automated tests on this release with a 99% pass rate.

MAJOR HIGHLIGHTS

• Added upgrade support from beta release
• Fixed issue with lists in custom registration form
• Fixed issue with ignore words in Italian and French
• Fixed issue with site export in multi-language site
• Fixed issue where parameters in return URL were malformed
• Fixed issue in sitemap for multi-language site
• Fixed issue where control panel did not render links correctly in SSL offload environments
• Fixed issue where pages with future start date were inaccessible
• Fixed multiple password reset issues
• Fixed issue where site settings could be duplicated
• Fixed issue where dismissing all notifications removed messages as well
• Fixed issue where file link for missing file caused exception
• Fixed issue where localized portal settings were not getting applied when switching languages
• Fixed issue where admin was unable to change interface language
• Fixed issue where page name uniqueness was applied cross language
• Fixed multiple scheduler issues

Best DotNetNuke Hosting Recommendation

ASPHostPortal.com provides its customers with Plesk Panel, one of the most popular and stable control panels for Windows hosting, as free. You could also see the latest .NET framework, a crazy amount of functionality as well as Large disk space, bandwidth, MSSQL databases and more. All those give people the convenience to build up a powerful site in Windows server. ASPHostPortal.com offers DotNetNuke hosting starts from $5. We also guarantees 30 days money back and guarantee 99.9% uptime. If you need a reliable affordable DotNetNuke Hosting, we should be your best choice.

How to Create a Backup of DNN and The Database

This topic is very important and requires a bit of planning, especially if you do not have direct access to your database server to perform your own backups. In the following sections I will first talk about what you must backup and why some of those items are very important. I will then discuss how to perform a DNN backup and SQL Server backup.  Finally I will discuss options available for third party modules for performing backups for individuals that do not have direct access to their servers.

What to Backup?

Simply put, it is a best practice to backup your entire DotNetNuke directory on the web server as well as a full backup of the database. Some people will say that you can get by with only backing up the "portals" folder, this is not correct! To successfully restore a DotNetNuke installation you must ensure that you have all module .dll and other code files you also must have the same validation and decryption keys.  I have found that the only real method to keep your data safe is to create a backup with all files.  Given the limited file size of the core DNN installation I have not found this to be a hinderance, especially since the additional files that exist in my website are all related to the content available within and is something I must have a backup.

Performing The Backup

Performing a backup of DotNetNuke is a fairly easy two step process. First I will discuss backing up the DNN installation directory, then I will discuss options available for backing up the database.

Backing up The DotNetNuke Directory

You have two options when backing up the DotNetNuke directory. If you have direct access to the server, you can simply right click on the DotNetNuke directory and select "Send To:" -> "Compressed (Zipped) Folder". This applies for most versions of the windows operating system. You will then have a file named dnn441.zip where dnn441 was your directory name. This zip file will contain all needed backup files, you will want to store this in a safe location.

If you do not have direct access to the server and can only access it via FTP you will have an additional step to obtain a zip file for your site. You will want to connect to your FTP site and COPY all files to a temporary location on your local computer. Once all files have been copied you will want to create a zip file including ALL files and folders that were just downloaded.

NOTE: if using a program such as WinZip for zipping, ensure that the "Use Folder Names" option is enabled so that the folder structure is preserved within your zip archive.

Backing up The DotNetNuke Database

To backup the database you must have access to the database server and the file system of the database server. If you are in a hosted environment you will need to rely on your hosting provider to obtain a backup, or you will need to look into a potential third party solution to backup the database from within DotNetNuke. If you have full access to the server please use one of the below sets of instructions to backup your database..

Backing up a Database with SQL Server and Enterprise Manager

Follow the below steps if you wish to create a databse backup file from Enterprise Manager for SQL Server using Enterprise Manager.

• Navigate to your specific database in Enterprise Manager
  
• Right click on the database and select "All Tasks" -> "Backup Database.."
  
• Ensure that "Complete" is selected for the backup type
  
• Click the "Add" button in the "Destination" section
  
• In this section provide a full file path to the desired backup file, typically named databasename.bak where databasename is your database name
  
• Click "Ok" to generate your backup, you will receive a success notice upon completion
  
• You will now have a full backup file containing all tables and data for your database.

Best DotNetNuke Hosting Recommendation

ASPHostPortal.com provides its customers with Plesk Panel, one of the most popular and stable control panels for Windows hosting, as free. You could also see the latest .NET framework, a crazy amount of functionality as well as Large disk space, bandwidth, MSSQL databases and more. All those give people the convenience to build up a powerful site in Windows server. ASPHostPortal.com offers DotNetNuke hosting starts from $5. We also guarantees 30 days money back and guarantee 99.9% uptime. If you need a reliable affordable DotNetNuke Hosting, we should be your best choice.

Dear All,
I hope every one worked with this control before with .net, yesterday i just use with DNN and i want to share this with you to use the Multiview controller with the control files.

Register your controls

<%@ Register Src="~/DesktopModules/BV Admin GenerateForm/Admin_GenerateForm_01_SelectCustomer.ascx" TagName="step1" TagPrefix="ke" %>
<%@ Register Src="~/DesktopModules/BV Admin GenerateForm/Admin_GenerateForm_02_AddParent.ascx" TagName="step2" TagPrefix="ke" %>
<%@ Register Src="~/DesktopModules/BV Admin GenerateForm/Admin_GenerateForm_03_AddChild.ascx" TagName="step3" TagPrefix="ke" %>
<%@ Register Src="~/DesktopModules/BV Admin GenerateForm/Admin_GenerateForm_04_formPreview.ascx" TagName="step4" TagPrefix="ke" %>
<%@ Register Src="~/DesktopModules/BV Admin GenerateForm/Admin_GenerateForm_05_SucessMessage.ascx" TagName="step5" TagPrefix="ke" %>

Here .acx are all controllers

Now you add the Multiview controller with your master ascx file

<asp:MultiView ID="MultiView1" runat="server">
        <asp:View ID="firstStep" runat="server">
                <ke:step1 ID="step1_tab" runat="server"></ke:step1>
        </asp:View>
        <asp:View ID="secondStep" runat="server">
                <ke:step2 ID="step2_tab" runat="server"></ke:step2>
        </asp:View>
        <asp:View ID="thirdStep" runat="server">
                <ke:step3 ID="step3_tab" runat="server"></ke:step3>
        </asp:View>
        <asp:View ID="forthStep" runat="server">
                <ke:step4 ID="step4_tab" runat="server"></ke:step4>
        </asp:View>
        <asp:View ID="fifthStep" runat="server">
                <ke:step5 ID="step5_tab" runat="server"></ke:step5>
        </asp:View>

</asp:MultiView>

Code behind:

For Display the active tab
 MultiView1.SetActiveView(firstStep);
"firstStep" is a view ID with i mentioned above

I hope the code will help you.

Best DotNetNuke Hosting Recommendation

ASPHostPortal.com provides its customers with Plesk Panel, one of the most popular and stable control panels for Windows hosting, as free. You could also see the latest .NET framework, a crazy amount of functionality as well as Large disk space, bandwidth, MSSQL databases and more. All those give people the convenience to build up a powerful site in Windows server. ASPHostPortal.com offers DotNetNuke hosting starts from $5. We also guarantees 30 days money back and guarantee 99.9% uptime. If you need a reliable affordable DotNetNuke Hosting, we should be your best choice.

How to Use the Text DotNetNuke Skin Object

DotNetNuke is a web content management system based on Microsoft .NET. The DNN Platform Edition is open source. DNN is designed for multi-tenancy and supports an unlimited number of websites, either as root websites or for portals in a parent-child configuration. The platform's skinning feature separates content from design-related files for easier customization. Skins make it simple to maintain a common look and structure across related sites without advanced programming knowledge. DNN's core functionality can be expanded with modules for common elements, such as those for e-commerce. The software enables parent-child website resource sharing and management using specially-formed symbolic links.

What is a Skin Object?

First of all, a skin object is an ASP.Net user control that is used in DNN skins to provide a limited feature.  For example, the search box, menu, login link, copyright statement, and more, are all skin objects.  They allow a skin designer to include dynamic content without having to know how to build the content itself, or knowing any programming.

Other than the previous description, this post will assume that you know how to create and package your own skin.

Text Skin Object

The Text skin object itself is a very useful feature in skinning, as it allows you to include localized text, while not having to create a copy of the skin for each language, or using any other number of workarounds.

For example, if you have static text next to your login skin object that says, “Welcome, “ then you might want to have alternatives for another language, if you plan to support it.

I am going to use that example for the rest of this post.

The Code

There is minimal code needed to implement the Text skin object.  If you’re using an HTML skin, then you would simply need to do the following:

<object id="dnnTEXT-Welcome" codetype="dotnetnuke/server" codebase="TEXT">

    <param name="Text" value="Welcome, " />

    <param name="CssClass" value="NormalBold" />

    <param name="ResourceKey" value="Welcome.Text" />

    <param name="ReplaceTokens" value="False" />

</object>

If you are using a ASCX skin, then you would need two updates.  First, put this line of code into the top section of the source:

<%@ Register TagPrefix="dnn" TagName="TEXT" Src="~/Admin/Skins/Text.ascx" %>

Next, put this code into the appropriate spot of the source in the skin:

<dnn:TEXT runat="server" id="dnnTEXT-Welcome" Text="Welcome, "

CssClass="NormalBold" ResourceKey="Welcome.Text" ReplaceTokens="False" />

Resource Files

Next, you need to make sure your skin has resource files.  In your skin package, you should have a folder namedApp_LocalResources.  This folder will contain the necessary files to tell your skin the appropriate text to use for the skin object when the specific language is asked for during page request life cycle.

If your skin file is named index.ascx or index.html, then your default resource file for English would be namedindex.ascx.resx.  If your additional supported language is French, your filename might be index.fr-FR.ascx.resx.

The English file code would be something like this:

<?xml version="1.0" encoding="utf-8"?>

<root>

  <data name="Welcome.Text">

    <value>Welcome, </value>

  </data>

</root>

The respective code for the French language file might look like this:

<?xml version="1.0" encoding="utf-8"?>

<root>

  <data name="Welcome.Text">

    <value>Accueil, </value>

  </data>

</root>

Text Skin Object Properties Explained

There are a few properties that you’ve seen in the previous examples that you might be wondering about.  Here is an explanation of those properties:

• Runat – (required, ASCX only) The value must be ‘server’ 
  
• Id – (required) This is a unique name for the tag, much like in standard HTML 
  
• Text – (optional) This value will be used as the default, should an appropriate resources file for the current language not be found 
  
• CssClass – (optional) This value is the name of a CSS class that will be available to the rendered HTML page to stylize the text in the web browser 
  
• ResourceKey – (required) This value references the id (name) of the text to retrieve from the resources file 
  
• ReplaceTokens – (optional) This true/false value will tell DNN to look for system tokens and replace them with the appropriate text

To move a MS-SQL database to another server for DotNetNuke installation, you can follow this steps :

• Make sure to backup SQL(MS-SQL) server data and DNN(dotnetnuke) files before moving.
• Copy DNN files to the new server, restore the SQL data into the new SQL server.
• Delete the default DNN user login after you restore the SQL backup on the new server, I had experience that the old DNN user cannot login to the new SQL server and return a page is unavailable when you load the web pages.
• The SQL server may not let you delete the old user so easily, following are the steps I used.  First, delete the old user from the Security thread on the SQL server.  Then locate the DNN database and looks for the old user on the security thread within the DNN database.  You cannot delete the old user now, you must go to the roles, and locate the database roles thread, under this thread, there are several items with the word aspnet in the beginning.  Click its property and look for its owner, most likely it will be the old user name, change all these aspnet items owner to dbo.  After you made these changes, you can delete the old user from security thread.
• After fully deleted all old user items, you can create a new user login in the Security thread (not that one on the DNN database), map the new user to the DNN database and with db_owner right.
• After you created the new user, go to DNN database -> roles -> database roles, locate all aspnet items and change the owner to the new user you just created.
• After these changes, your SQL should be okay.

Best DotNetNuke Hosting Recommendation

ASPHostPortal.com provides its customers with Plesk Panel, one of the most popular and stable control panels for Windows hosting, as free. You could also see the latest .NET framework, a crazy amount of functionality as well as Large disk space, bandwidth, MSSQL databases and more. All those give people the convenience to build up a powerful site in Windows server. ASPHostPortal.com offers DotNetNuke hosting starts from $5. We also guarantees 30 days money back and guarantee 99.9% uptime. If you need a reliable affordable DotNetNuke Hosting, we should be your best choice.

DNN 7 allows customization of the registration form via an easy interface, with intellisense. You just select "Custom" for Registration Form Type in Admin - Site Settings - User Account Settings tab and you can add all the fields you like to your registration form.

At the moment of writing, this doesn't seem to work well with custom registration properties (i.e. fields you have created yourself via the "Profile Settings - Add New Profile Property button below on the same tab). If you try to type a custom property's name on the Registration Fields box, it just won't come up (although it's been reported that properties of datatype "Text" do come up).

In order to make these properties available to your registration form until a fix is applied to this, you can use SSMS (provided that you have access and experience using it) and do the following:

•     Go to your DNN database
•     Open the "PortalSettings" table for edit and find the record that has the value "Registration_RegistrationFields" in the "SettingName" field
•     You'll see that the "SettingValue" field is a comma-delimited list containing the field aliases of the properties that are to be displayed on the custom registration form. Add the aliases of your own fields in the list.
•     Update the table and go to your DNN installation (as the Host user), and click on Tools - Clear Cache
•     If everything goes well, you'll see that the "Registration Fields" box now contains your properties too, and they will appear normally on the registration form.

Another way to do this is to use the Host - SQL section on your DNN installation. To see the current profile properties that are displayed on the custom registration form, type this into the Script box and click "Run Script":

SELECT
SettingValue
FROM  {databaseOwner}{objectQualifier}PortalSettings
WHERE
SettingName = 'Registration_RegistrationFields'

In order to add one or more fields at the end of the list, you must run something like this (where 'MyField' is your custom field's alias). Remember the comma and use no spaces.

UPDATE 
{databaseOwner}{objectQualifier}PortalSettings
SET
SettingValue = SettingValue + ',MyField'
WHERE
SettingName = 'Registration_RegistrationFields'

After you run it, go to Tools and click Clear Cache and you will see your fields on the "Registration Fields" box in the Admin - Site Settings - User Account Settings tab.

If you still need more power and customization with your custom registration page, take a look at the Dynamic Registration module from Datasprings - at the moment of writing this, version 5.0 has just been released for DNN 7.x.

Best DotNetNuke Hosting Recommendation

ASPHostPortal.com provides its customers with Plesk Panel, one of the most popular and stable control panels for Windows hosting, as free. You could also see the latest .NET framework, a crazy amount of functionality as well as Large disk space, bandwidth, MSSQL databases and more. All those give people the convenience to build up a powerful site in Windows server. ASPHostPortal.com offers DotNetNuke hosting starts from $0. We also guarantees 30 days money back and guarantee 99.9% uptime. If you need a reliable affordable DotNetNuke Hosting, we should be your best choice.

Error:

On a new install of DNN 7, when you click on managementand edit buttons, rather than editing you are redirected to the home page (home.aspx).

Happens when using the below actions:

    Edit Page > Edit This Page
    Modules > Add a module
    Uploading images and logos to the Appearance section of Site Settings

Solution:

    After installation is complete, create a duplicate of the web.config and rename web.config.orig
    Open web.config and find the modules node in the <system.webServer> section and add the paramenter below

        <modules runAllManagedModulesForAllRequests="true" >

Test for functionality

Now when you click on the edit page > edit this page button, you should see the edit tools. This may repair a number of other issues revolving around editing, popups, dragging, uploading images & logos, etc.

Best DotNetNuke Hosting Recommendation

ASPHostPortal.com provides its customers with Plesk Panel, one of the most popular and stable control panels for Windows hosting, as free. You could also see the latest .NET framework, a crazy amount of functionality as well as Large disk space, bandwidth, MSSQL databases and more. All those give people the convenience to build up a powerful site in Windows server. ASPHostPortal.com offers DotNetNuke hosting starts from $0. We also guarantees 30 days money back and guarantee 99.9% uptime. If you need a reliable affordable DotNetNuke Hosting, we should be your best choice.

You recently upgrade your DNN version, after upgrade you cannot login to your website and get "A critical error has occurred. An unexpected error has occurred".

The database upgraded successfully and you don't see any errors in the server logs.

Step by Step to Fix it :

In your web.config try changing

<members defaultProvider="AspNetMembershipProvider">
<providers>
 <clear />

    <add name="AspNetMembershipProvider" type="DotNetNuke.Security.Membership.AspNetMembershipProvider, DotNetNuke.Provider.AspNetProvider" providerPath="~\Providers\MembershipProviders\AspNetMembershipProvider\" />
      </providers>
    </members>

to

<members defaultProvider="AspNetMembershipProvider">
      <providers>
        <clear />
        <add name="AspNetMembershipProvider" type="DotNetNuke.Security.Membership.AspNetMembershipProvider, DotNetNuke" providerPath="~\Providers\MembershipProviders\AspNetMembershipProvider\" />
      </providers>
    </members>

Best DotNetNuke Hosting Recommendation

ASPHostPortal.com provides its customers with Plesk Panel, one of the most popular and stable control panels for Windows hosting, as free. You could also see the latest .NET framework, a crazy amount of functionality as well as Large disk space, bandwidth, MSSQL databases and more. All those give people the convenience to build up a powerful site in Windows server. ASPHostPortal.com offers DotNetNuke hosting starts from $0. We also guarantees 30 days money back and guarantee 99.9% uptime. If you need a reliable affordable DotNetNuke Hosting, we should be your best choice.

When upgrading from DNN 6.x to DNN 7.x, the installation wizard seems to miss an important setting in the web.config.  It also does not delete old DLLs from the /bin/ folder.  Because you are performing an upgrade rather than a clean installation, there are two versions of the AspNetMembershipProvider available, and the web.config may point to the wrong one.

Here is the fix.  Update your web.config to change the AspNetMembershipProvider section so that it uses the DotNetNuke.dll assembly instead of the DotNetNuke.Provider.AspNetProvider.dll assembly.

    <members defaultProvider="AspNetMembershipProvider">
      <providers>
        <clear />
        <add name="AspNetMembershipProvider"
          type="DotNetNuke.Security.Membership.AspNetMembershipProvider,
          DotNetNuke.Provider.AspNetProvider"
          providerPath="~\Providers\MembershipProviders\AspNetMembershipProvider\" />
      </providers>
    </members>

After removing “.Provider.AspNetProvider” from the configuration, everything should work fine.

FREE ASP.NET Hosting for DotNetNuke Recommendation

ASPHostPortal.com provides its customers with Plesk Panel, one of the most popular and stable control panels for Windows hosting, as free. You could also see the latest .NET framework, a crazy amount of functionality as well as Large disk space, bandwidth, MSSQL databases and more. All those give people the convenience to build up a powerful site in Windows server. ASPHostPortal.com offers DotNetNuke hosting starts from $0. We also guarantees 30 days money back and guarantee 99.9% uptime. If you need a reliable affordable DotNetNuke Hosting, we should be your best choice.

DotNetNuke will use jQuery help popup model along with picture rotating results. These are good plus a massive improvements with systems such as flash. On the other hand it's not difficult to find two separately coded jQuery modules that may cause conflicts when utilized on the same page while as each other.

The reason

The reason typically is actually which modules might be hard coded to use their version of jQuery. (Think of jQuery as a plugin that's needed for your code to insert onto the web page).

Your library which powers jQuery is often updated to include new capabilities. Sooner version of DotNetNuke do have no capacity to insert jQuery or even reference reference it as “part” of the core of DNN.

Consequently for almost any component published for early DNN types, this library plugin for jQuery would have to be bundled or referenced to an online source like the free Google jQuery reference.

If a pair of module are generally on the same site and calling various types of jQuery into play, it is likely which one of several modules will certainly discord and also neglect to perform appropriately. Often it's going to be the harder advanced or even later on built module  which fails.

DotNetNuke Solution

The treatment for this is to built one common core library into your core ofDotNetNuke, and let modules along with other code to reference this specific single source when calling on the jQuery library for every reason.

DotNetNuke have included jQuery as an option inside the host adjustments, to allow it become loaded from there.

They run a release version on the jQuery library that is certainly presumably kept up to date with releases of DotNetNuke. The past version involving DotNetNuke 5x show this.

Modules can easily either call up this library, or use their own library.

How Modules Use DNN version of jQuery or Their Own version

Well created code or perhaps modules in most cases have the setting that permits you to reference this HOST DNN version of jQuery, or call into play in the version that shipped with the module.

With our quests, we work with a tab placing that seems as if this:

If this “Load jQuery” can be ticked, the module uses the jQuery library that may be shipped with the module.

If the option is just not ticked, the module uses the DotNetNuke bundled version associated with jQuery.
Greatest Resolution

As soon as conflicts happen, the best way to resolve it's in order that both quests are referencing the same jQuery selection version. The quick way to get this done is in order that both modules are certainly not using their own version, or inside our case “Load JQuery” is just not CHECKED.

And, ensure that any some other modules are also not referencing their own version associated with jQuery but need to this hosted jQuery. (Talk towards the module developer on how to get this done. )

Other Possible Troubles

1. One of many modules may need a feature that may be more advanced compared to the the organised jQuery version. In that case, a afterwards jQuery library must be referenced. Allowing this to be done, DotNetNuke include allowed that you reference the URL regarding another version of jQuery.

One example is, in our Mushroom Image module regarding DotNetNuke, the rotating effect requires a later version of jQuery compared to the last version of DotNetNuke 5x recommendations. 1.4.4. To set a afterwards version, you just find a online resource this way Google organised jQuery selection:

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

And also enter that will URL into your HOST jQuery adjustments.

a couple of. Another issue is that there could be a conflict in the jQuery script employed to call this module behavior. We include included the ability to customize this script employed to reduce clash.

Naturally this is an selection for innovative users, and not all quests have that feature.

What's the Get hold of Message?

Each time a conflict occurs, there is generally no “developer” to blame, but alternatively an incompatibility involving the ways which the jQuery will be called. Don’t assume which the last element installed is to blame.

In most cases the conflicts can be resolved with all the steps outlined above. This assumes which the modules mounted have similar flexibility once we do inside our modules.

FREE ASP.NET Hosting for DotNetNuke Recommendation

ASPHostPortal.com provides its customers with Plesk Panel, one of the most popular and stable control panels for Windows hosting, as free. You could also see the latest .NET framework, a crazy amount of functionality as well as Large disk space, bandwidth, MSSQL databases and more. All those give people the convenience to build up a powerful site in Windows server. ASPHostPortal.com offers DotNetNuke hosting starts from $0. We also guarantees 30 days money back and guarantee 99.9% uptime. If you need a reliable affordable DotNetNuke Hosting, we should be your best choice.