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.

Have you found yourself needing to programatically clear DotNetNuke (DNN) cache but were dismayed to learn newer DNN versions no longer depend on an easily-cleared cookie? Here's a simple alternative to force the cache to clear

Clearing Cache
So you have a require to clear a DNN user's cache but you're employing a newer version of DNN that no longer retailers factors in an easily-cleared cookie. If this describes you then you're possibly:

• Bypassing DNN's "correct" mechanisms (built-in objects and the Data Access Layer) by directly calling SQL stored procedures.
• Querying straight through to data stored in SQL tables.

As an admin you have DNN's built-in alternatives for clearing cache and even "resetting the application domain". Your finish users, even so, lack these options and, actually, why would you desire customers to possess to accomplish something particular? You desire a solution that's hidden and automatic.

Cut to the chase:
Under is actually a link to a cost-free DNN7 module that does one factor: flush the cache. Drop the module on a web page, set the VIEW permissions for whatever group(s) you need the module to become active for and that's it.

The module itself has no configuration choices. The only genuine point to think about is who you would like the module to fire for. Users that are not logged in have no user-specific data to flush so you'll be able to rule out "Unverified Users" and, by extension, "All Users" (that is the mixture of "Registered Users" and "Unverified Users"). In most situations you will probably want to set the VIEW permission to "Registered Users".

Note that you simply do *not* want to use this module on pages with a lot of site visitors. Continuously flushing cache is definitely an outstanding way to cripple a busy web site. This module is greatest used on infrequently-visited pages (like a custom "user update" web page).

Additional Thoughts: Short and Sweet
The module necessary less than 10 minutes to create using DNN's constructed in "module creator" function (that indicates I designed it from within a DNN site utilizing absolutely nothing but the web browser) and less than 5 minutes to create the deployment package making use of DNN's constructed in "create package" feature but... those are topics for another day.

Best DotNetNuke Hosting Recommendation

In DNN website, there is a portal.css file for each portal present inside the web site. In some cases we need to modify the css classes of custom modules to create it responsive with skin from the portal, in that case its usually much better to keep these css classes in portal.css rather than Module.css of custom module, so that it may be effortlessly managed by modifying the portal.css from site interface without going towards the module code file.

Step by step approach to access the portal.css file are offered under.

Step 1

Log in to the DNN website as a Host. Go to the Admin -> Site Settings as shown in the image below.

Step 2

Make sure you have selected Stylesheet Editor from the menu.

Step 3

Upon clicking Stylesheet Editor, a text editor will come which contains all the css classes present in portal.css file.
Here, we can add any new classes or modify existing classes.

For example, we need border color based on the skin color and we have used style_cat_border css class in our custom module to style the border. So, in order to add border style that will fit with the skin, its always a nice to add this class in portal.css class rather than Module.css file of module.

Once can easily change it by going to portal.css of website as shown in the image below. In the end click on Save Style Sheet to implement the changes.

As we've got observed within the above explanation, it often greater to help keep all these css classes which needs to be changed determined by skin from the DNN website inside the portal.css in the internet site which in turn may be very easily managed via internet site interface.

Best DotNetNuke Hosting Recommendation

Today I will explains about Integrating the google tag manager (GTM) into DNN. Google has an awesome scripts-management engine called GTM (Google Tag Manager). Though it talks about managing tags, in reality it actually manages script-integration. Particularly Google-scripts (like Adwords and tracking stuff), but also jQuery and similar.

How does it work? In general you create a “set” of “tags” (read: scripts w/parameters) in a web-interface provided by google. Then you integrate that set with some iFrame/Script-HTML-snippet in your layout. If one day you would like to add another tag or change the tag-integration-rules, you do this on the GTM-System, without having to modify your page. Note that the GTM-System also allows various rules, like automatically integrating different scripts depending on the page that is being viewed; adding custom parameters etc. – very powerfull.

The integration is a bit tricky with DNN, because it uses an iFrame which must be added right after the tag and before the default tag.
To learn more about GTM, visit the Google Tag Manager website.
To integrate your tag, use this snippet in your default.ascx (remember to replace the xxxx with your code). Note: this works with DNN 6+ and 7+.

<script runat="server">
     protected override void OnInit(EventArgs e)
     {
         base.OnInit(e);
         var tp = (CDefault)Page;
         tp.FindControl("Body").Controls.AddAt(0, new Literal() { Text = "<!-- Google Tag Manager --><noscript><iframe      src='//www.googletagmanager.com/ns.html?id=GTM-XXXX'height='0'width='0'style='display:none;visibility:hidden'></iframe></noscript><script>function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start':newDate().getTime(),event:'gtm.js'});varf=d.getElementsByTagName(s)[0], j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src='//www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f);})(window,document,'scr" + "ipt','dataLayer','GTM-XXXX');</scr" + "ipt><!-- End Google Tag Manager -->" });      
     }
 </script>

By the way – the easiest way to test and use this is by trying the DNN App for GTM I created.

Best DotNetNuke Hosting Recommendation

ASPHostPortal.com

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/month only. 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.

The much more I find out the a lot more excited I get about how slick it's and so straightforward to work with. It can genuinely give some rally cool features to your site as well as give a good way for me as a programmer to circumvent some tasks that can be hard to accomplish using server side programming.

Today I was presented using a process on an current internet site using the DotNetNuke publishing platform. The consumer has designed a form employing a module inside the framework. The kind is used to order some stuff and the visitor has to click quite a few verify boxes based on what they wish to order. There is certainly also ha a bunch of pages with data concerning the items. Every web page includes a direct hyperlink on i to acquire towards the order web page. Now, when the visitor clicks this link the check box for that distinct item ought to be checked, simply to make issue simpler.

I have no intention on going in towards the framework to alter the behaviour from the module so I thought I'd attempt some jQuery on this.

Initial off the only thing I truly know is the fact that the order kind will have a header like this "<h1>Order form</h1>" (potentially the module can exist on several pages, even several times around the same web page) and that the item page may have the item name within the url, which is also the text on the verify box.

My thought was that very first verify when the order kind exist around the web page by looking for the header then check the referrer url and evaluate this towards the verify box names. This is the code:

$(document).ready(function()
{
if($("h1:contains(Order form)"))
{
setOrderCheckboxes();
}
});

// Automatically set checkboxes if the visitor previously viewed
// a page named the same as the checkbox
function setOrderCheckboxes()
{
$("input[type='checkbox']").each(function()
{
// The text element is always a sibling directly following the checkbox
var checkboxName = $(this).next().text();

// DNN url replaces characters in PageName
checkboxName = checkboxName.replace(" ", "").replace("-", "");

if(document.referrer.indexOf(checkboxName) != -1)
{
$(this).attr("checked", true);
}
});
}

Best DotNetNuke Hosting Recommendation

DNN 7 finally comes with pop up login window but many people actually fooled by its tricky method to perform that. The DNN 7 pop up login module is developed employing Jquery to load the default login web page through iframe!

For that reason, to modify the design and style of the login panel, you will ought to look for 3 major parts:

1. The pop up windows design.
2. The login page.
3. The Login module.

Initial, in case you wish simply to disable to pop up login, all you will need to do is disable “Enable Pop-up” below Website Setting > Usability Settings. *This setting is site wide.

If you only wish to disable the only login module pop up, you'll ought to locate this file in
root\admin\Skins\Logo.ascx.cs
Then look for line 119-122 and take away it.

if (PortalSettings.EnablePopUps && PortalSettings.LoginTabId == Null.NullInteger)
{
    loginLink.Attributes.Add("onclick", "return " + UrlUtils.PopUpUrl(loginLink.NavigateUrl, this, PortalSettings, true, false, 300, 650));
}

To modify the pop up window design, all the style definitions are situated in default.css in /portals. folder. Appear for something that has .dnnforms I’ll leave this in an additional subject.

Modifying the Login web page is straightforward, essentially it really is is dependent upon your skin on the web page. If you’re making use of pop up window, I advise you to create a blank skin for the login page to speed up the loading. (As it utilizes iframe to load whole login web page whilst displaying only the login form within the pop up window, maintain the login web page easy to speed it up)

Now the tough element, Login Module. You may want to locate these 2 main files:

root\DesktopModules\AuthenticationServices\DNN\Login.ascx and

root\DesktopModules\AuthenticationServices\DNN\Login.ascx.cs

Whilst you are able to pretty much leave the .cs file alone, the .ascx file is essential for modifying the html structure from the module. The very good factor about DNN 7 login module would be the tableless coding structure where it is possible to play about with the style only using CSS and Jqeury.

The new installation of DNN 7 will not shipped with LiveID and OpenID Authentication any longer. I will leave that portion out for now.

Until next time then, really feel cost-free to ask me if you necessary much more sophisticated guide. I’ll attempt my greatest to help.

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.

DotNetNuke has already established itself as 1 from the most well-liked too as preferred net content management systems, primarily based on Microsoft. Net. DotNetNuke web sites are identified to provide outstanding user knowledge while also letting the brands enhance their identity. The current trend is the fact that of integrating this content material management system with that of Microsoft SharePoint, of which the newest version has not too long ago come out within the form of SharePoint 2013.

The integration is really valuable for the companies inside a number of methods. Right here is really a short overview of how the integration of DotNetNuke with SharePoint can be executed with accomplishment.

Powerful Document Management with SharePoint

SharePoint is undoubtedly probably the most preferred at the same time as even sought- after program for document management, helpful for businesses of varying size or nature. Now, this platform is constructed into cloud, which allows maximum storage and accessibility. Consequently, the experts in a group have an chance to share as well as collaborate on apparently massive amounts of data and documents. Moreover, the platform integrates efficiently with Outlook and this enables enhancement in the significance on the social tools. All this results in a very carefully organized atmosphere. The group members can also convert the raw data into critical interactive reports.

Integration of DotNetNuke with SharePoint

The top thing about integrating the web content management method together with the net application improvement platform is the fact that the two of them integrates quite seamlessly. An automatic integration implies that no additional efforts are essential when it comes to operating the method. The DNN Neighborhood can merge together with the platform inside a rather hassle- totally free manner by indicates of using the custom modules. The primary thought, here, is always to design and style a method that enables the platform to communicate from behind a firewall with all the folks facing the website. Now, all this implies that the documents could be pushed in to the portal around the DotNetNuke website with larger degree of safety and efficiency. Simultaneously, the filter rules can be made to track down the individual documents to discover as to exactly where they go.

DNN Enterprise and SharePoint Connector

In situations where the platform is utilized as the document management program, integration of the identical with DotNetNuke Enterprise Edition is really of real rewards. The custom integration saves a lot of income in the enterprise while investment that is produced is actually worthy.

The DNN Enterprise SharePoint connector comes up as a powerful and considerable function, supporting each 2007 and 2010 versions of the platform. The firewall problems can be avoided at the same time. Content, around the other hand, stays fresh and is published directly from the SharePoint Document Library. It is the DotNetNuke role- based security network that performs the crucial function of safeguarding the published documents.

Generating Use on the SharePoint Folder Provider

The SharePoint Folder is particularly beneficial in integration with DotNetNuke 6. It enables the DNN customers to store at the same time as synchronize the files contained inside the document libraries, located in 2010 version of this platform.

Here is an overview on the characteristics of this Folder as well as the way it aids:

The communication amongst the net application improvement platform and the DotNetNuke six becomes more rapidly and more direct by virtue from the folder. It paves the way for a number of providers to indicate to different document libraries from either the equivalent platform based internet sites or in the various ones.

The SharePoint Folder facilitates quite a few functionalities such as addition cum deleting of folders, uploading, downloading, renaming of files as well as synchronization of the files and folders. Above all, this Folder really acts as a powerful base for numerous DNN modules, which make use on the DotNetNuke file technique. Custom SharePoint development teams can help you build projects within allocated budgets and time schedules.

Best DotNetNuke Hosting Recommendation

ASPHostPortal.com

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.

I have been seeing a big number of concerns not too long ago with regards to DotNetNuke functionality and items that will be done to help improve the overall performance in the internet site. Usually these questions surround the SiteLog and EventLog tables so I thought I'd post a number of simple queries which you can run to assist hold your database lean that will preserve your DotNetNuke website running at peak efficiency.

Website Log

I'll start off using the Internet site Log table, the website log functionality isn't a single that I truly utilize in my site, nonetheless for all those of you who use it in yours you are going to need to hold an eye on it, I have noticed that right after the log has grown to more than about 4-5 thousand records that you could begin to notice some efficiency decreases. Furthermore if you're like myself and have turned off the internet site log I found out that it will not necessarily clean itself up in case you turned it off, therefore in my case I had 1000 lingering records, which just unnecessarily improved the size of my database.

To check the amount of records within your Site Log use the following query

SELECT Count(*)
FROM SiteLog

To find the oldest record in the site log use the following

SELECT MIN([DateTime])
FROM SiteLog

Soon after you've viewed this details you can establish your necessary course of action. In my case since the internet site log is disabled on all portals I simply deleted all records in the table employing a basic delete statement. Within your case you could only want to purge certain records but that determination is outdoors the scope of this short article.

Event Log

The Occasion log shops portal certain event details like logins, invalid login attempts and actual errors. If you have a pretty active portal this table can grow very big really quickly. For my sites with their visitors of about 100-120 guests per day I have noticed an EventLog of over 2000 records within a two.five month period. Now unless you happen to be auditing logins or undertaking particular tracking you are able to normally rid yourself of those records without much impact. You'll be able to purge these portal by portal via the "Event Viewer" inside DotNetNuke, or it is possible to view and modify records by way of the database. Beneath I'll give you two valuable queries.

To determine the number of records, as well as the quantity of records per portal. Note, inside the benefits in the per portal query, you are going to discover a lot of entries listed having a NULL portal id, that is for DNN installation wide things, like scheduler and application events.

--Overall total
SELECT COUNT(*)
FROM EventLog

--Total by portal (null is not portal specific)
SELECT LogPortalId, COUNT(*)
FROM EventLog
GROUP BY logPortalId

To identify the oldest records you can use one of the following queries, again an overall minimum and a per portal minimum will be found

SELECT MIN(LogCreateDate)
FROM EventLog

SELECT LogPortalId, MIN(LogCreateDate)
FROM EventLog
GROUP BY logPortalId

Once again for deleting these records the decision truly depends upon your portals use on the Occasion Log and any require for user login auditing. In my case I once again don't require this details and at present I've resolved all of my routine errors that had been taking place, for that reason I removed all records in my listing across all sites. I try to complete this at the very least as soon as as month to ensure that the table size has been decreased.

Viewing DB Size

If you would like to view the size of one's database files you are able to make use of the query below to view the size of every single file for the present database.

SELECT *
from SYSFILES

Making use of these ideas you'll be able to start to acquire a better understanding of the database size and you can assist handle it and preserve your DotNetNuke website running at peak efficiency!

Best DotNetNuke Hosting Recommendation

ASPHostPortal.com
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/month only. 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.