First off  - I apologize if this naive post. This is my first DotNetNuke install and I'm still getting used to working with it. With that disclaimer... I'm just trying to get a blog module up and running.

I am running DNN version 04.08.00 and version 03.04.00 of the blog module. Everything I've played with so far seems to work with the exception of the blog entry editor. Whenever I attempt to use it I get the "Error: Edit Entry is currently unavailable message."

I googled about a bit and found the issue with the mistyped 'e', but when I checked out my EditEntry.ascx it was already fixed in my version.

After digging around a bit I found the event log and was able to pull the stack trace. I googled a bit more using some keys from the trace, but didn't find anything useful. Is this a known issue?

InnerException: The base class includes the field 'txtDescription', but its type (DotNetNuke.UI.UserControls.TextEditor) is not compatible with the type of control (ASP.controls_texteditor_ascx).
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.Web.Compilation.BaseTemplateCodeDomTreeGenerator.BuildFieldDeclaration
StackTrace:
Message: DotNetNuke.Services.Exceptions.ModuleLoadException: The base class includes the field 'txtDescription', but its type (DotNetNuke.UI.UserControls.TextEditor) is not compatible with the type of control (ASP.controls_texteditor_ascx). ---> System.Web.HttpParseException: The base class includes the field 'txtDescription', but its type (DotNetNuke.UI.UserControls.TextEditor) is not compatible with the type of control (ASP.controls_texteditor_ascx). ---> System.Web.HttpParseException: The base class includes the field 'txtDescription', but its type (DotNetNuke.UI.UserControls.TextEditor) is not compatible with the type of control (ASP.controls_texteditor_ascx). at System.Web.Compilation.BaseTemplateCodeDomTreeGenerator.BuildFieldDeclaration(ControlBuilder builder) at System.Web.Compilation.BaseTemplateCodeDomTreeGenerator.BuildSourceDataTreeFromBuilder(ControlBuilder builder, Boolean fInTemplate, Boolean topLevelControlInTemplate, PropertyEntry pse) at System.Web.Compilation.BaseTemplateCodeDomTreeGenerator.BuildSourceDataTreeFromBuilder(ControlBuilder builder, Boolean fInTemplate, Boolean topLevelControlInTemplate, PropertyEntry pse) at System.Web.Compilation.TemplateControlCodeDomTreeGenerator.BuildMiscClassMembers() at System.Web.Compilation.BaseCodeDomTreeGenerator.BuildSourceDataTree() at System.Web.Compilation.BaseTemplateBuildProvider.GenerateCode(AssemblyBuilder assemblyBuilder) at System.Web.Compilation.AssemblyBuilder.AddBuildProvider(BuildProvider buildProvider) --- End of inner exception stack trace --- at System.Web.Compilation.AssemblyBuilder.AddBuildProvider(BuildProvider buildProvider) at System.Web.Compilation.BuildProvidersCompiler.ProcessBuildProviders() at System.Web.Compilation.BuildProvidersCompiler.PerformBuild() at System.Web.Compilation.BuildManager.CompileWebFile(VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.UI.TemplateControl.LoadControl(VirtualPath virtualPath) at System.Web.UI.TemplateControl.LoadControl(String virtualPath) at DotNetNuke.UI.Skins.Skin.InjectModule(Control objPane, ModuleInfo objModule, PortalSettings PortalSettings) --- End of inner exception stack trace ---

Thanks for the reply. Ironically, I had just finished uninstalling/reinstalling the blog module when I read your post. Unfortunately, the reinstall didn't take care of the issue, but it was an obvious thing to try first.

When reinstalling didn't cut it, pulled down the blog module off my server and started tracing up from the txtDescription control. It was a really short trace. The txtDescription control is a dnn:texteditor that normally lives in ~/controls/TextEditor.ascx. Since the exception was complaining about the base type, I downloaded the TextEditor.ascx file to see what it was derived from. Imagine my surpise when I opened the file and found... nothing. The file was empty -both on my client and on the server. I'm guessing it must have been an issue with my ftp when I originally moved DotNetNuke up to the server.

I went back to my original DotNetNuke download, pulled out the TextEditor.ascx file and pushed it up to the server. After a quick app restart, everything seems peachy -although I'm still wondering why it fell back to the plain old textbox control when it couldn't find the DNN class. I did notice that when I tried adding an entry after I uploaded the correct TextEditor.ascx, I got a type conflict for controls_texteditor_ascx in the ASP namespace. I'll have to dig a bit more for my own edification.