We have an instructional video published to help new users install a DotNetNuke module to a DNN 5 + website. The module shows you the simple steps you need to follow to install any of our DotNetNuke Modules. See the instructions in installing a DotNetNuke Module in DNN 5 +
Much has been written about the DotNetNuke performance settings, and well frankly the is a lot of bad information running around the web about what all the settings mean and do. I’m not about to jump into a discussion, but rather tell you what we believe are the best settings for a public facing website hosted from a Windows 2008 servers without a proxy. First of all you will need to determine if the web server IIS settings have been configured to compress data servers from your site. This is easy. 1. Login as host and look in the Performance Settings for the “Compression Setting” and ensure it is turned off. 2. Then visit this site: http://www.seoconsultants.com/tools/compression Enter your URL of the website you are playing with, and check compression. The result will look like this, if your content is uncompressed. or this if it is compressed. Take not of… Read More »DotNetNuke Performance Settings
There are a few people around the net with this problem. Site Settings Error Error: Site Settings is currently unavailable. DotNetNuke.Services.Exceptions.ModuleLoadException: Cannot insert the value NULL into column ‘DefaultLanguage’, table ‘tendollar.dbo.tdb_Portals’; column does not allow nulls. UPDATE fails. The statement has been terminated. —> System.Data.SqlClient.SqlException: Cannot insert the value NULL into column ‘DefaultLanguage’, table ‘tendollar.dbo.tdb_Portals’; column does not allow nulls. UPDATE fails. The statement has been terminated. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) at DotNetNuke Product: DotNetNuke Community Edition The DotNetNuke version you are running 05.01.02 (51) We have posted a solution on our DotNetNuke Knowledge Base website. Search on “Site Settings is currently unavailable”
DotNetNuke DNN Exception Details: System.Web.HttpException: Server cannot modify cookies after HTTP headers have been sent.
We had a client with this error in their DotNetNuke Website: Server Error in ‘/’ Application. ——————————————————————————– Server cannot modify cookies after HTTP headers have been sent. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.Web.HttpException: Server cannot modify cookies after HTTP headers have been sent. Source Error: An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. Stack Trace: [HttpException (0x80004005): Server cannot modify cookies after HTTP headers have been sent.] System.Web.HttpResponse.BeforeCookieCollectionChange() +8710212 System.Web.HttpCookieCollection.Add(HttpCookie cookie) +24 System.Web.Security.AnonymousIdentificationModule.OnEnter(Object source, EventArgs eventArgs) +1792 System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +68 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +75 For DNN the problem turned out to be in the… Read More »DotNetNuke DNN Exception Details: System.Web.HttpException: Server cannot modify cookies after HTTP headers have been sent.
PageLoadException errors in the DNN Site Log, and problems with users selecting profile data options in the DotNetNuke profile date area caused many page load exceptions. The solution is as simple as changing the Host Settings / Performance Settings.