Admit it. Those little questionmark help icons are ugly. Even if you replace the icon image with something more fancy, you still have to display them everywhere, even at the front-end (for example, the Feedback module uses them). And, if you’re developing for more than one language, that creates an awful lot of work for you, since you have to translate all texts that appear as tooltips when you hover over the icons.

There’s an easy way to hide them, though, and it’s site-wide. It will also apply to any third-party modules that use the dnn label control for providing labels for form controls.

Go to controls\labelcontrol.ascx and change the following line:

   <asp:image id="imgHelp"  runat="server" imageurl="~/images/help.gif" enableviewstate="False" />

to
   <asp:image visible="false" id="imgHelp"  runat="server" imageurl="~/images/help.gif" enableviewstate="False" />

That’s right. A visible=”false” attribute and the icons will disappear.

Also, if you notice that the labels are shifted to the left a bit (especially in IE), then go two lines above and change the line:

<span style="width:15px">

to

<span style="width:0px">

Or delete the span tag all together.

You can find a relevant thread on DotNetNuke.com with some more tips and tricks for the labelcontrol.ascx file here.
Have fun!

Best Recommended DotNetNuke Hosting

ASPHostPortal.com is the leading provider of Windows hosting and affordable DotNetNuke Hosting. DotNetNuke Hosting from ASPHostPortal.com provides a safe, reliable and performance-driven foundation for your DotNetNuke website. DotNetNuke is the perfect Content Management System for managing and developing your website with one of ASPHostPortal’s Hosting plans. ASPHostPortal has ability to support the latest Microsoft and ASP.NET technology, such as: WebMatrix, WebDeploy, Visual Studio 2015, .NET 5/ASP.NET 4.5.2, ASP.NET MVC 6.0/5.2, Silverlight 6 and Visual Studio Lightswitch, ASPHostPortal guarantees the highest quality product, top security, and unshakeable reliability, carefully chose high-quality servers, networking, and infrastructure equipment to ensure the utmost reliability.

DotNetNuke equips developers with some of the most robust and powerful frameworks; crucial for building effectual Web applications desirable for eCommerce in DotNetNuke. Once these prerequisite components, especially the templates for Visual Studio and the framework for source edition are effectively installed, the actual process of development for DotNetNuke (DNN) modules becomes exceedingly fast and repeatable, as well as ready for instant use.

Furthermore, no or very little cost is involved in development of eCommerce in DotNetNuke modules as the templates, express editions and framework of the Visual Studio are commonly available free of cost. All you actually need for your eCommerce in DotNetNuke is Visual Studio, either Express or some other licensed edition; DotNetNuke Starter Kit which is available on the website of DotNetNuke; SQL Server, again either Express or some other licensed edition; and a working installation of DotNetNuke for your eCommerce in DotNetNuke.

Building an Ecommerce in DotNetNuke Module

To start with, you will need to open the DotNetNuke website development copy in your Visual Studio. Then simply add a plain file to your eCommerce in DotNetNuke project by making use of a DotNetNuke Dynamic Module template, which comes fully installed with your DotNetNuke Starter Kit package. Open your web.config file to trace the compilation node. Then simply proceed to add a node titled codeSubDirectories under compilation. Add one more item under the codeSubDirectories by using name of your module entered by you in the last step, in the following format: <add directoryName="ModuleName"/>.

Now, go to the Solution Explorer and proceed by locating the DesktopModules directory. Here, you will find a fresh directory that has been created by Dynamic Module template, below your DesktopModules directory. Rename the directory with the same module name used by you in your previous steps. You must next log-in into the DotNetNuke website, opened previously by you in the Visual Studio, by using the facility of a host account provided for the purpose. Under the main menu of this host account, select the Module Definitions option, and then select the Create New Module option. Now, you will need to fill-up this module form by making use of the same module name used by you in the steps followed earlier.

After that is done, click on the Add Control of the form for Create New Module. From the drop-down list, click select on the file that has been added to it by Dynamic Module template. This file represents module name that was specified in your previous steps; only with the extension:.ascx added to it. You now need to open this.ascx file in the Visual Studio. It will display both a code-behind view and design created by the module template. You can add functionality to this code-behind file as deemed suitable to your eCommerce in DotNetNuke. Visual and layout elements may also be added to your design view, if desired. Before making an attempt to create the module, it is advisable to verify DotNetNuke portal installation functionality.

Best Recommended DotNetNuke Hosting

ASPHostPortal.com is the leading provider of Windows hosting and affordable DotNetNuke Hosting. DotNetNuke Hosting from ASPHostPortal.com provides a safe, reliable and performance-driven foundation for your DotNetNuke website. DotNetNuke is the perfect Content Management System for managing and developing your website with one of ASPHostPortal’s Hosting plans. ASPHostPortal has ability to support the latest Microsoft and ASP.NET technology, such as: WebMatrix, WebDeploy, Visual Studio 2015, .NET 5/ASP.NET 4.5.2, ASP.NET MVC 6.0/5.2, Silverlight 6 and Visual Studio Lightswitch, ASPHostPortal guarantees the highest quality product, top security, and unshakeable reliability, carefully chose high-quality servers, networking, and infrastructure equipment to ensure the utmost reliability

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.

Today when i install the DNN 7 then i found and issue in edit mode after installation.

The problem is when i go to edit mode the page refresh with out enabling the edit mode, after a short research on Google i found the solution. I hppe it save your time

1. Backup your web.config
2. Open your web.config in a text editor
3. Within the web.config file, find the <system.webserver><modules> section.
4. If the <modules> section says <modules runAllManagedModulesForAllRequests="false"> change it to <modules runAllManagedModulesForAllRequests="true"
   OR if it just says <modules>, change it to <modules runAllManagedModulesForAllRequests="true">
5. Save the config file.
6. Retry by refreshing the page and trying again.  You can also test this out by trying to a do a journal post (which also uses the services framework in an authenticated way.

If some how its will not work then, you must change the control panel bar from control bar to ribbon bar

Here are the steps
Go to host tab > Host settings > Other settings > Change control panel bar from control bar to ribbon bar

Regards

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.

Often when writing DNN Service Framework methods (based on ASP.NET Web API) you find yourself writing the same boiler plate error-handling code.  Figure 1 shows an example of this boiler-plate code.

Figure 1: An example of a Service Framework Action Method

[HttpPost]
public HttpResponseMessage DeleteTask(TaskDTO taskDTO)
{
try
{
using (var context = DataContext.Instance())
{
var repo = context.GetRepository();
var task = repo.GetById(taskDTO.TaskId, ActiveModule.ModuleID);

repo.Delete(task);
var result = new {Result = "success"};
return Request.CreateResponse(HttpStatusCode.OK, result);
}
}
catch (Exception exc)
{
var result = new { Result = exc.Message };
return Request.CreateResponse(HttpStatusCode.InternalServerError, result);
}
}

This is great that we write code with explicit error handling, but it can get repetitive.  Fortunately ASP.NET Web API provides a way to make this a lot easier – to encourage us to use good error-handling practices.  Web API provides an ExceptionFilterAttribute base class.  This attribute can be applied at the class level or at the method level.  If applied at the class level it applies to all action methods. in the class. The ExceptionFilterAttribute base class has one method OnException which is called if there is an unhandled exception in the action method.

In order to provide support for DNN’s localization framework, the Dnn Services Framework includes a subclass of this base class – DnnExceptionFilterAttribute.  This class provides two properties which gives the developer the ability to provide a MessageKey, and a LocalResourceFile.  Each of these has a default – MessageKey defaults to {ControllerName}_{ActionName}.Error where ControllerName is the name of the controller class and ActionName is the name of the action method where the error occurs, and LocalResourceFile defaults to the global Exceptions.resx resource file.

Lets see how our Delete action method will look if we use the DnnExceptionFilterAttribute.

Figure 2: The Delete Action Method modified to use DnnExceptionFilter

[HttpPost]
[DnnExceptionFilter(MessageKey = "DeleteTask.Error")]
public HttpResponseMessage DeleteTask(TaskDTO taskDTO)
{
using (var context = DataContext.Instance())
{
var repo = context.GetRepository();
var task = repo.GetById(taskDTO.TaskId, ActiveModule.ModuleID);

repo.Delete(task);
var result = new {Result = "success"};
return Request.CreateResponse(HttpStatusCode.OK, result);
}
}

This is a lot less work to do – while still retaining excellent error-handling.

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.

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.

Dear All, Today when i install the DNN 7 then i found and issue in edit mode after installation. The problem is when i go to edit mode the page refresh with out enabling the edit mode, after a short research on Google i found the solution. I hppe it save your time.

1. Backup your web.config
2. Open your web.config in a text editor
3. Within the web.config file, find the <system.webserver><modules> section.
4. If the <modules> section says <modules runAllManagedModulesForAllRequests="false"> change it to <modules runAllManagedModulesForAllRequests="true"> or
   
5. If it just says <modules>, change it to <modules runAllManagedModulesForAllRequests="true">
6. Save the config file.
7. Retry by refreshing the page and trying again. You can also test this out by trying to a do a journal post (which also uses the services framework in an authenticated way.

If some how its will not work then, you must change the control panel bar from control bar to ribbon bar

Here are the steps
Go to host tab > Host settings > Other settings > Change control panel bar from control bar to ribbon bar

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.

In DotNetNuke installing and uninstalling modules is quite considerably automated so normally there is no need to to this manually. But at times this needs to be done manually, by way of example when uninstalling failed because of an SQL error.

Also, DotNetNuke is lacking a mechanism to invoke module methods for cleaning up on uninstall. This means all files and configuration the module produced won't be touch. So I will also highlight under other steps involved in uninstalling a module.

Just before Uninstalling a Module

Either you happen to be uninstalling automatically employing DNN functions or manually, make certain to verify every single item beneath to avoid issues which you would run into later:

• Remove Skin Objects
  If the module lets you use it as a Skin Object, undergo all ascx files in DNN skin folders (/Portals/[portal id]/Skins) and take away the @Register directive at the best and all occurrences from the that tag inside that file
• Check web.config references
  Some modules/components also do changes to web.config to register their own handlers. One such instance are URL Rewrite elements - they need to register both an URL Provider plus a URL Rewriter. Make an effort to search the element you're uninstalling by its name or parts of its name.
• Check dependencies
  Some modules on the market depend on other modules/components that need to currently be installed on that portal. Removing the dependency prior to the module could leave the internet site offline and you'd have to go in on FTP and SQL Server to manually fix the error.
• Verify Files
  Even though this may possibly not create problems it's greater which you know what elements leave on disk following uninstall so you are able to determine what to complete with that (delete, backup, and so on). It's typical for modules to write their information within the portal folder (by default Portals/[portal id]/) folder. This can consist of settings, temporary files, documents produces by the module and so on. As an example, Search Boost leaves the Lucene Index at "/Portals/_default/Lucene[ID String]". This has small worth to keep it since it may be recreated at any time by Search Increase. Nevertheless, a gallery module could store its photos and thumbnails and you may possibly wish to preserve that.
• Backup
  This ought to be 1st in your list, much better to be certain than sorry. Ahead of undertaking key configuration changes (at least to production atmosphere) ensure to backup the database and files on disk.

Manually Cleaning the Database

All modules deploy with SQL uninstall scripts. They are located in [Website Folder]/DesktopModules/[ModuleName]/Uninstall.SqlDataProvider. Usually the SQL consists of two unique tokens that generally get replaced by DNN:

• {databaseOwner}  - you can replace this with empty text, this will work in 99% of the cases
• {objectQualifier} - you were asked for this during DotNetNuke installation wizard. If you don't remember it, look into the database at the table names and see if they all have the same prefix. If they do, that's the objectQualifer. Make sure to copy the underscore as well if it exists (for example the objectQualifier "dnn_" not "dnn")

As soon as you created the replace run the SQL in SQL Management Studio or in Host>SQL (and ensure to verify Run as Script).

Right after this, there could still be some leftovers, but sadly they are not so straightforward to locate particularly once you don't know what to appear for. But typically modules add their very own prefix to all database objects they generate. For instance, all My Tokens tables and stored procedures possess the prefix "avtMyTokens_". After you spot this, it is possible to run an SQL query like below to find out all database objects matching that pattern:

select * from sysobjects where name like '%avtMyTokens%'

Note the xtype column will tell the type of the object (U - user table, P - stored procedure, F - foreign key and so on).

DotNetNuke equips developers with a few of the most robust and strong frameworks; crucial for creating effectual Web applications desirable for eCommerce in DotNetNuke. Once these prerequisite components, particularly the templates for Visual Studio and the framework for supply edition are properly installed, the actual procedure of development for DotNetNuke (DNN) modules becomes exceedingly rapidly and repeatable, also as ready for immediate use.

In addition, no or very little expense is involved in improvement of eCommerce in DotNetNuke modules as the templates, express editions and framework on the Visual Studio are frequently obtainable free of charge of expense. All you in fact need to have for the eCommerce in DotNetNuke is Visual Studio, either Express or some other licensed edition; DotNetNuke Starter Kit that is available around the website of DotNetNuke; SQL Server, once again either Express or some other licensed edition; plus a functioning installation of DotNetNuke for the eCommerce in DotNetNuke.

Building an Ecommerce in DotNetNuke Module

To start with, you will need to open the DotNetNuke website development copy inside your Visual Studio. Then merely add a plain file to your eCommerce in DotNetNuke project by creating use of a DotNetNuke Dynamic Module template, which comes fully installed with your DotNetNuke Starter Kit package. Open your internet.config file to trace the compilation node. Then simply proceed to add a node titled codeSubDirectories below compilation. Add 1 much more item below the codeSubDirectories by using name of one's module entered by you in the final step, inside the following format: <add directoryName="ModuleName"/>.

Now, go to the Answer Explorer and proceed by locating the DesktopModules directory. Here, you will find a fresh directory which has been created by Dynamic Module template, under your DesktopModules directory. Rename the directory using the exact same module name utilised by you inside your previous measures. You must next log-in in to the DotNetNuke website, opened previously by you inside the Visual Studio, by using the facility of a host account offered for the purpose. Under the main menu of this host account, select the Module Definitions selection, and then select the Produce New Module option. Now, you'll need to fill-up this module type by producing use on the exact same module name used by you inside the measures followed earlier.

Following which is done, click around the Add Handle on the form for Generate New Module. In the drop-down list, click pick on the file that has been added to it by Dynamic Module template. This file represents module name that was specified within your previous measures; only with all the extension:.ascx added to it. You now want to open this.ascx file within the Visual Studio. It is going to display both a code-behind view and design developed by the module template. You can add functionality to this code-behind file as deemed suitable to your eCommerce in DotNetNuke. Visual and layout components might also be added for your design view, if desired. Ahead of producing an attempt to generate the module, it's advisable to verify DotNetNuke portal installation functionality.