HTML Editor Non-Functional Post Upgrade of DNN

Description of bug

After performing an upgrade of DNN Platform the HTML Editor fails to display, or displays missing icons, until manual steps are taken to update the files/configurations within the editor itself.

Steps to reproduce

This has been validated on multiple installations, currently using two different starting points for upgrade.

• Start with a working DNN Installation (Validated on 9.6.2 and 9.8.1)
• Upgrade to DNN 9.10.2
• HTML Editor will be broken, the exact state of broken

Current behavior

The HTML editor either displays with missing icons and “might” work, or the editor 100% fails to display. (This will depend on the configuration and settings of the editors. If a plugin is missing the editor fails to display. Otherwise it will display sans icons)

You can fix this by going into this folder /Providers/HtmlEditorProviders/DNNConnect.CKE/js/ckeditor

And then reviewing these two sub folders;

Old = 4.5.3 New = 4.15.1

The issue seems to stem from the following discrepancies

• Icons - Completely missing from 4.15.1
• Images - Completely missing from 4.15.1
• Plugins - Some of the plugins in 4.5.3 are missing, which causes failures. This doesn’t impact every installation
• Skins - Come of the skins from 4.5.3 are missing, this can cause issues depending on exact issues.

Expected behavior

You should be able to upgrade DNN Platform and the HTML Editor should still be functional without manual intervention, especially intervention that requires direct access to the site.

Error information

You will see multiple errors of failure to load files, or missing images

[sawest]

I just upgraded to 9.11.2 from 9.8.0. I experienced the exact same issue as @cklenk showed above. I had to copy two plugin folders from the 4.5.3 plugin folder to the 4.18.0 plugin folder (newsarticlelinks and iframedialog). After these were copied the editor is now working. It doesn’t appear the #5205 fixed this issue.

[cklenk]

Totally understand @WillStrohl!! This was on a dev site and not launched yet so that’s why we didn’t have an ssl on it. But good to know! I can certainly log a new issue for this if you want.