Apache Logging Service and Log4Net

Log4net is a popular open source framework of the Apache Logging Project to log application errors for web sites. Log4net is part of the Apache Logging Services project at the Apache Software Foundation. The Logging Services project is intended to provide cross-language logging services for purposes of application debugging and auditing. The Apache log4net project DotNetNuke and Evoq Starting with DNN v6 […]

Apache Logging Service and Log4Net Read More »

DotNetNuke Editors

What is the current default for your site Open the web.config and find this line <htmlEditor defaultProvider=”<value>”> <value> is the name of the provider.  You can look it up on this list. History of HTML Editor Providers Editor Provider Name Notes Freetextbox Ftb3HtmlEditorProvider Default from v2.0.0 to v3.0.0. FCKEditor FckHtmlEditorProvider  Default until v5.3.3. No longer developed, its url redirects to

DotNetNuke Editors Read More »

DotNetNuke Errors

Common Errors Web page fails to load when Telerik is used The Telerik editor was used as the primary editor in DNN from 2009 to 2013.  The Telerik failure error was usually caused by a failure to update the web.config file. To fix this: Verify the Telerik.Web.UI.dll version from the website bin directory using Windows Explorer. Go to root directory

DotNetNuke Errors Read More »

DotNetNuke Upgrade Path

DotNetNuke is one of the easier platforms to upgrade but with a long version history the path to go from an old version to a new version isn’t clear. It is important to not skip major versions when upgrading as the code to upgrade core components can’t handle the infinite possibilities. The basic plan Before starting an upgrade its best

DotNetNuke Upgrade Path Read More »

Scroll to Top