November
20
2008
Written by: hipsterdoofus at 2:19 pm in the Web Development category.
Some links to remember and also a post to push the previous one down the page. The <pre&rt; tag isn’t being nice with the template I’m using and I don’t have time to fix it at the moment.
November
20
2008
Written by: hipsterdoofus at 1:20 pm in the Web Development category.
While experimenting with the wiki component in one of my portals today, I received an error when trying to add a post via the FCK editor, Could not load type 'DotNetNuke.HtmlEditor.FckHtmlEditorProvider.fckStyles'. More specifically:
[HttpException]: Could not load type 'DotNetNuke.HtmlEditor.FckHtmlEditorProvider.fckStyles'.
at System.Web.UI.TemplateParser.GetType(String typeName, Boolean ignoreCase, Boolean throwOnError)
at System.Web.UI.TemplateParser.ProcessInheritsAttribute(String baseTypeName, String codeFileBaseTypeName, String src, Assembly assembly)
at System.Web.UI.TemplateParser.PostProcessMainDirectiveAttributes(IDictionary parseData)
[HttpParseException]: Could not load type 'DotNetNuke.HtmlEditor.FckHtmlEditorProvider.fckStyles'.
at System.Web.UI.TemplateParser.ProcessException(Exception ex)
at System.Web.UI.TemplateParser.ParseStringInternal(String text, Encoding fileEncoding)
at System.Web.UI.TemplateParser.ParseString(String text, VirtualPath virtualPath, Encoding fileEncoding)
[HttpParseException]: Could not load type 'DotNetNuke.HtmlEditor.FckHtmlEditorProvider.fckStyles'.
at System.Web.UI.TemplateParser.ParseString(String text, VirtualPath virtualPath, Encoding fileEncoding)
at System.Web.UI.TemplateParser.ParseReader(StreamReader reader, VirtualPath virtualPath)
at System.Web.UI.TemplateParser.ParseFile(String physicalPath, VirtualPath virtualPath)
at System.Web.UI.TemplateParser.ParseInternal()
at System.Web.UI.TemplateParser.Parse()
at System.Web.UI.TemplateParser.Parse(ICollection referencedAssemblies, VirtualPath virtualPath)
at System.Web.Compilation.BaseTemplateBuildProvider.get_CodeCompilerType()
at System.Web.Compilation.BuildProvider.GetCompilerTypeFromBuildProvider(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.Compilation.BuildManager.GetVirtualPathObjectFactory(VirtualPath virtualPath, HttpContext context, Boolean allowCrossApp, Boolean noAssert)
at System.Web.Compilation.BuildManager.CreateInstanceFromVirtualPath(VirtualPath virtualPath, Type requiredBaseType, HttpContext context, Boolean allowCrossApp, Boolean noAssert)
at System.Web.UI.PageHandlerFactory.GetHandlerHelper(HttpContext context, String requestType, VirtualPath virtualPath, String physicalPath)
at System.Web.UI.PageHandlerFactory.System.Web.IHttpHandlerFactory2.GetHandler(HttpContext context, String requestType, VirtualPath virtualPath, String physicalPath)
at System.Web.HttpApplication.MapHttpHandler(HttpContext context, String requestType, VirtualPath path, String pathTranslated, Boolean useAppConfig)
at System.Web.HttpApplication.MapHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
After messing around with it for a while, I found a workable and easy solution on the DNN forums which amounted to “deleting the fck folder completly from the providers/htmleditorproviders folder and replacing it with the fck folder from the install package.”
November
7
2008
Written by: hipsterdoofus at 2:40 pm in the Web Development category.
I was just planning on doing a simple blog post. Unfortunately, I wanted to reference a previous post and made the discovery that in designing my blog layout, I didn’t account for a way to access past posts. A huge oversight, it seems - a rookie mistake. Which got me to thinking that I needed to make a quick fix to the blog to rectify the situation. Except that there’s no easy solution afforded by the Blogger (classic) template that I’m currently using. So instead of the simple post that I was planning on making, I’m writing this bitchy one to complain about Blogger and once again consider moving this whole damn thing over to WordPress. I am (supposed to be) a web developer after all.
Tags: Blogger, WordPress