This morning I upgraded from 4.5.1 to 4.5.3 and now any page that has the fckEditor on it, crashes for me. Here is the event log info: I turned loggin on and checked the htmleditor section in web.config. I used the upgrade dnn install.
Bill
AssemblyVersion: 04.05.03
PortalID: 0
PortalName: The LOGOS Store
UserID: 1
UserName: host
ActiveTabID: 46
ActiveTabName: Newsletters
RawURL: /Admin/BulkEmail/tabid/46/Default.aspx
AbsoluteURL: /Default.aspx
AbsoluteURLReferrer:
UserAgent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.0.3705; .NET CLR 1.1.4322; InfoPath.1; .NET CLR 2.0.50727)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: bd3b8e35-2d4e-4884-9894-20b990eb8870
InnerException: Could not load file or assembly 'DotNetNuke.FckHtmlEditorProvider' or one of its dependencies. The module was expected to contain an assembly manifest.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.RuntimeTypeHandle._GetTypeByName
StackTrace:
Message: System.BadImageFormatException: Could not load file or assembly 'DotNetNuke.FckHtmlEditorProvider' or one of its dependencies. The module was expected to contain an assembly manifest. File name: 'DotNetNuke.FckHtmlEditorProvider' at System.RuntimeTypeHandle._GetTypeByName(String name, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMark& stackMark, Boolean loadTypeFromPartialName) at System.RuntimeTypeHandle.GetTypeByName(String name, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMark& stackMark) at System.RuntimeType.PrivateGetType(String typeName, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMark& stackMark) at System.Type.GetType(String typeName, Boolean throwOnError, Boolean ignoreCase) at System.Web.Compilation.BuildManager.GetType(String typeName, Boolean throwOnError, Boolean ignoreCase) at DotNetNuke.Framework.Reflection.CreateType(String TypeName, String CacheKey, Boolean UseCache, Boolean IgnoreErrors) WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
Source:
Server Name: WSS31