About DotNetNuke
DNN Developer?
If you're a DotNetNuke Developer and are looking for Modules, you'll want to check out our DotNetNuke Modules page.

DNN (aka DotNetNuke) is an advanced content management system (CMS) specifically designed for websites, Intranet deployments, and web application development. Administrators are given complete control of their content, layout, security and membership and are provided with a powerful set of tools to maintain a dynamic and interactive site.

As an active member of the DNN open-source community, Efficion devotes a great deal of effort in contributing time and modules for the improvement of the DNN software and community as a whole.

Through the combined efforts of the DNN community, we have created a software framework that is reliable, flexible, and most of all, a powerful solution for meeting the needs of many different types of organizations. Learn More...

DNN Consultants with years of Experience

Back in 2004, when Efficion was just starting up and open source Content Management Systems were a fairly new concept, Efficion performed an exhaustive evaluation of the most popular CMS's in order to choose the best to build our business around. We chose DotNetNuke.

Built on top of the wonderful ASP.NET framework, it was technically superior, had a great community, a growing ecosystem, excellent leadership, had a great, extensible architecture, and was a very solid product. To this day, I feel strongly we made the right choice.

Since then, we've built the majority of our websites, intranets, and web applications on top of DNN. We offer a full range of services. Visit our services page to learn more.

DotNetNuke Related Articles

Adding PayPal button to DotNetNuke

Don't get duped into buying a module just to add a PayPal button to your DotNetNuke website. Paypal will actually generate the code/HTML you need for you and then you can just paste that text into the Source view of a Text/HTML module.

Here's some sample code that you can modify with your own information:


But, if you log in to your PayPal account, there's a section where they will generate this code for you with a variety of options. Comments (0)

When you Dynamically Load a Control, you must explicitly set the LocalResourceFile

This is something I've learned and forgotten at least 4 times. Writing these types of things here helps me remember and seem to help quite a few other people as well. So...

Usually in DotNetNuke, if you want to associate a resource file with your control, you just create a resource file with the same name as the ascx file plus the .resx extension and place it in your App_LocalResources directory. DotNetNuke and/or ASP.NET auto-magically associates the file with your code and it just works.

However, every time that I create a control that dynamically loads other controls, I spend 30 minutes looking at names and file placement and... trying to figure out why the resource file doesn't seem to be loading. Eventually, it comes to me, for dynamically loaded files, you must explicitly set the LocalResource file.

To do this add the following line to your PageLoad function in your dynamically loaded control:

 LocalResourceFile = DotNetNuke.Services.Localization.Localization.GetResourceFile(this, "controlfilename.ascx");

To learn more about DNN Module Localization, check out the DotNetNuke Module Localization Guide.

Comments (0)

DotNetnuke: Is user an admin / administrator

DotNetNuke makes it easy to determine if the currently logged in user is an administrator (aka admin) or any other role for that matter. All you need to do is call the following: PortalSecurity.IsInRole("Administrators") or PortalSecurity.IsInRole("MyRoleName"). This function should return the boolean value very quickly as everything it needs is already in memory. You can call this from either the code behind or the ascx file (e.g. Visible='<%#PortalSecurity.IsInRole("Administrators")%>').

This can be very useful for determining whether or not to show a control or content meant only for the right groups eyes.

Comments (1)

Is your DotNetNuke site running slow

A common performance issue in some versions of DotNetNuke

Is your DotNetNuke site running ridiculously slowly and consuming massive amounts of your processor? It might be stuck in a bit of a catch 22... The scheduler is trying to clear the ScheduleHistory table, but it can't because the ScheduleHistory table is too full.

Read More... Comments (2)

Custom Toolbars in the FCKEditor Provider for DNN

When it comes to the toolbars for Rich Text Editors for clients to use to update there own sites, it is my firm belief that less is more. By default, the toolbars seem to be cluttered with endless options that rarely get used and in the end just make it harder to find the options users do need.

The FCKEditor Provider for DotNetNuke is great overall and exposes almost everything you need to set it up just they way you want it, including setting up different custom toolbars for different types of users (determined by role). But I haven't found much clear and concise documentation for adding your own custom toolbars. Here is how I do it...

Read More... Comments (0)
Page 9 of 10First   Previous   4  5  6  7  8  [9]  10  Next   Last