We found an issue with what is the current release version of DotNetNuke Blog module 04.01.00 or 04.01.01. First up, we don’t know what the version number should actually be, as the compiled version on the download is 04.01.00 but the source code is referenced as 04.01.01. We presume there is some difference, but who knows what it is. Anyway The Problem The problem is that any forms on a page that run the blog module, will not allow form data to be validated. By validated, we are talking about ensuring a number is entered in a number field and text in a name filed etc. The cause is the blog module is using an old ASP.Net 1.0 validation function. While it should be using ASP.NET 2.0 with the updated validation behaviours as found here: http://msdn.microsoft.com/en-us/library/0ke7bxeh.aspx With this mistake, if you use Page.Validate on ASP.NET 2.0, page validation groups are… Read More »Problem With DNN Blog Module 04.01.00 – 01
DotNetNuke can use jQuery to enable popup style and image rotator effects. These are great and a big improvements on technologies like flash. However it is not hard to find two separately coded jQuery modules that can cause conflicts when used on the same page as each other. The Reason The reason in most cases is that modules can be hard coded to use their own version of jQuery. (Think of jQuery as a plugin that is required for the code to load onto the web page). The library that powers jQuery is often updated to include new features. Earlier version of DotNetNuke did not have any ability to load jQuery or reference it as “part” of the core of DNN. So for any module written for early DNN versions, the library plugin for jQuery needed to be included or referenced to an online source like the free Google jQuery… Read More »jQuery Conflicts in DotNetNuke Modules–Advanced Login
Could not load file or assembly ‘AjaxControlToolkit, Version=3.0.30930.28736, Culture=neutral, PublicKeyToken=28f01b0e84b6d53e’ or one of its dependencies. The located assembly’s manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) We were playing today with a trial module from another developer. Received the above error. After much mucking around, we found that the very specific version of the AjaxControlToolkit.dll file that came with the module, was not installed during the normal module setup. We extracted the file into the \bin\ directory on the site, and joy to the world. Strange that a specific version is required and that the 3.5 or 4.0 version does not work. This is how they referenced a specific version. Not a good way to program.
There are load of features and functions about DotNetNuke that tick us off. Some big, some small and some that are baseless. It never ceases to astound me why they do some features and functions so poorly. Today I had to write about a pet hate… Why when we go to the module definition page, do we see a list of “Upgrades?” with the painfully ugly Microsoft style highlighted version number. Really. Whoever built that system.. was that look the best you could come up with. It is painful enough that the stupid system does not allow third party developers to reference an RSS feed for their own updates. (Would have thought that was a no brainer). But why Microsoft Word frigging green highlight! How about something a little classier in the default look. Is this 1998? Think not! And for anyone reading this who thinks… “well you did not… Read More »How do I know DotNetNuke Corp is off the rails?
This sample examines the install of a dotnetnuke module to a dnn 5.6.0 website. We are using our Contact Details module as an example. We have recorded a video that we have uploaded to YouTube as an example file to assist with install.
How to easily add recaptcha to your dotnetnuke website. Easy… grab the latest version of Advanced Login module for DotNetNuke and you are on your way. We have enabled recaptcha in DotNetNuke with this module, making it as easy as ever to use the feature in your website. The advanced login module is available from our free dotnetnuke module download page.
DotNetNuke.Entities.Portals.PortalSettings..ctor(Int32 tabID, PortalAliasInfo objPortalAliasInfo) DNN 05.06.00
The Problem After updating a DNN site from 05.01.01 to DNN 05.06.00 we received the following error. ——————————————————————————– Object reference not set to an instance of an object. 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.NullReferenceException: Object reference not set to an instance of an object. 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: [NullReferenceException: Object reference not set to an instance of an object.] DotNetNuke.Entities.Portals.PortalSettings..ctor(Int32 tabID, PortalAliasInfo objPortalAliasInfo) +49 DotNetNuke.HttpModules.UrlRewriteModule.OnBeginRequest(Object s, EventArgs e) +2087 System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +68 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +75 We found that this is a bit of a reported… Read More »DotNetNuke.Entities.Portals.PortalSettings..ctor(Int32 tabID, PortalAliasInfo objPortalAliasInfo) DNN 05.06.00
Error The transaction log for database “domain.com” is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases
While accessing a DotNetNuke website today, I was getting this error all the time. Error The transaction log for database “domain.com” is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases Event ID 3001 Event code: 3001 Event message: The request has been aborted. Event time: 2/11/2010 12:28:32 PM Event time (UTC): 2/11/2010 1:28:32 AM Event ID: cc9168019d0b42cabde5ab8fa741927d Event sequence: 13 Event occurrence: 12 Event detail code: 0 I found this one a little perplexing. On further investigation I found that the transaction logging for the SQL server supporting this was massive. Around 980 meg when I would expect it to run around 15 meg. Initially I tried killing all processes with active connections to the database, but that did not have the desired result. (We all know what a pain that can be in SQL). So I set the database… Read More »Error The transaction log for database “domain.com” is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases