Hi Sebastin can you please give me some more info (im only learning) :)

FCKEditor stores the settings in database tables TabModuleSettings, ModuleSettings and PortalSettings. FCKEditor settings are easy to identify by its keys looking like "###FCK###" (or sth like this, I don't have database access atm). you may remove these settings to revert to standard configuration.

---

Cheers from Germany,
Sebastian Leupold

   

Speed up your DNN Websites with TurboDNN

 I have had a very similar problem on one of my sites, and I think I may have solved it.  The problem occurred after the upgrade from 4.9.? to 5.2.2.  Suddenly a lot of exceptions started popping up in the Event Viewer, involving both HTML encoding and reverse HTML encoding.  After trying the technique Nick used (to no avail) and running through the tables Sebastian mentioned, I finally got to thinking about the "Custom Editor Options."  This is what I did while logged on as host.

1.  I fired up an HTML module and edited the content.
2. Under the edit pane, I clicked on the link for "Show custom editor options."
3. In the new window, I made doggone sure I had the radio button for "Portal" selected.  Also, down below, I made sure the drop-box also had "Portal" selected before I saved anything.
4. I expanded the section "Other Editor Options."  There they were, two settings: "HTML Encode Output" and "Reverse HTML Encode Output"!  Both had "Default" selected.  I changed this to "Yes."
5. ...And I then applied this custom setting to the Portal.

When I went back and checked, the module had thrown the two exceptions when it loaded, but subsequent editing and loading did not generate any more exceptions.  I suspect that the software did not regard the "Default" options as proper Boolean entries.  Programmers wanted to give a Default option at Module and Instance levels, but probably didn't notice that defaulting all the way up to the portal level setting generated errors.

Hope this will work as a fix that doesn't require editing and uploading files or running SQL Update queries.  Stay well, everyone.