Hi all, fairly unfamiliar with the inner workings of DNN so the solution here may be obvious. After a quick upgrade to 9.6.1 to addres security vulnerabilities the HTML editor module on several of our sites broke in different ways. Some were addressed by updating the web config for CKE Editor, but that hasn't fixed this error. It may have to do with .dlls, I am unsure, so I thought I would get community input.
The error appears on the Edit Content page of the module, and reads:
Error: is currently unavailable. DotNetNuke.Services.Exceptions.ModuleLoadException: The base class includes the field 'dgHistory', but its type (DotNetNuke.Web.UI.WebControls.DnnGrid) is not compatible with the type of control (DotNetNuke.Web.UI.WebControls.Internal.DnnGrid). ---> System.Web.HttpParseException: The base class includes the field 'dgHistory', but its type (DotNetNuke.Web.UI.WebControls.DnnGrid) is not compatible with the type of control (DotNetNuke.Web.UI.WebControls.Internal.DnnGrid). ---> System.Web.HttpParseException: The base class includes the field 'dgHistory', but its type (DotNetNuke.Web.UI.WebControls.DnnGrid) is not compatible with the type of control (DotNetNuke.Web.UI.WebControls.Internal.DnnGrid). at System.Web.Compilation.BaseTemplateCodeDomTreeGenerator.BuildFieldDeclaration(ControlBuilder builder) at
(...etc, many more [...] at [...])
Before the upgrade the site was version 9.0.1 I believe, so it was probably the case that RadEditor was being used. I wasn't in charge of the upgrade to this instance, but other instances were upgraded in a similar way and aren't having the same problem. Unfortunately, reverting back is not an optio so any fixes will have to be done on the site as it is.
Would uninstalling the HTML editor module and then reinstalling the lastest version work as a fix? I had considered it but since 90% of the site is simply pages with the HTML editor I didn't want to risk something breaking in a worse way.
Big thanks for your quick reply. I do have access to the PB, so I've checked in Site Settings and the install is already using CKE. I had updated the web config previously as well.
Looking at my Extension settings the HTML module is at version 9.0.2, which is a far cry from the current version, so maybe that is where the problem lies.
Upgrading the module fixed the above problem, but now there are further issues. I'm only able to view Edit Content in the Basic Text Box view. The console is now throwing a "Uncaught ReferenceError: CKEDITOR is not defined" among a few other 500 internal server errors.
Going into Site Settings -> Site Behavior -> More to the HTMl Editor Manager page, it is set to DNNConnect.CKE but there is a message that reads "The current HTML Editor Provider is not supported by this version of the HTML Editor Manager."
If it's useful, the web.config includes:
htmlEditor defaultProvider="DNNConnect.CKE" providers clear add name="DotNetNuke.RadEditorProvider" type="DotNetNuke.Providers.RadEditorProvider.EditorProvider, DotNetNuke.RadEditorProvider" providerPath="~/DesktopModules/Admin/RadEditorProvider" settingsControlPath="~/DesktopModules/Admin/RadEditorProvider/ProviderConfig.ascx" add name="DNNConnect.CKE" type="DNNConnect.CKEditorProvider.CKHtmlEditorProvider, DNNConnect.CKEditorProvider" providerPath="~/Providers/HtmlEditorProviders/DNNConnect.CKE/" settingsControlPath="~/Providers/HtmlEditorProviders/DNNConnect.CKE/Module/EditorConfigManager.ascx" providers htmlEditor
Thanks Joe.
Comparing this site to another site upgraded at the same time, from the same version and with the same process (in fact, the problem site was a copy of this other site way back in the day): the "parent" site has a working HTML editor using CKEditor and all of the extensions the two sites share are the same version. I will also compare with a clean install, but the mystifying thing is the DNN sites having these problems are children of this "parent" site which has no problems. They all share almost the same set of extensions are are used for the same function, just with different coats of paint.
These Forums are dedicated to the discussion of DNN Platform.
For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:
Awesome! Simply post in the forums using the link below and we'll get you started.