I think Rad Editor is part of Telerik or Telerik itself Search Rad Editor you see.

Thanks Franc, but the point is that I have REMOVED both Telerik AND RadEditor from the site in question, and yet I am still getting these errors. In other words, something is still "looking" for these components, even though I was able to (seemingly successfully) uninstall them.

I am not very technical on this I have experienced some of the issue. In my case all the modules were up to date so I did the same you did, mine turned out that one on the up to date modules still needed RadEditor to work. I have also experienced that some of the modules are up to date to a specific Version of DNN. I would restore to the earlier working version, and verify with the module vendors. Or wait a little and see what others have to say. The forum is very responsive. 

@mitchelsellers, I have just discovered some problems with the DNN Documents module on this same site, and when checking GitHub I noticed the following, which I did not notice before:

Due to the major API changes that was included as part of the DNN 9.2.0 release, it is recommended that you upgrade the DNN Documents module to 7.0.0 BEFORE upgrading your website to DNN/Evoq 9.2.0, this will ensure that you do not encounter any upgrade errors related to this module.

I upgraded DNN Documents AFTER upgrading :-( and it's too late for me to go back and start again now. Two questions, then: Firstly, could this be part of (or entirely) the cause of the errors I'm getting on the site (e.g. could there be some legacy of the old DNN Documents left on the site that is still trying to instantiate RadEditor/Telerik?) and secondly, is there a way of "fixing" the DNN Documents module for dumb-a**es like me who didn't spot the disclaimer on GitHub before updating?

 

In general, I'd suggest always attempting to upgrade every third-party extension you have prior to upgrading DNN.  Now that you have found yourself in the next step...  

As far as the "too late to start now" part, are you able to upgrade the Documents module now?  What happens when you do?  Often, the "before" part is mostly to avoid disruptions to end-users.  They'll see a fatal exception until the upgrade is finally done.  

If you've upgraded already and still see exceptions, you'll probably want to create a new Issue in GitHub to determine the best path forward for you, based on the errors and log files you might have to help troubleshoot this to find your permanent solution.  

Thanks for the feedback, Will.

I was able to upgrade the Documents module without any obvious problems, and most of the pages where the module was used were working properly. It was just one page where the Documents module was there and had a list of "documents", which was totally blank!

Anyway, I decided to remove the Documents module completely from the site, just to be sure that the RadEditor/Telerik error was not related, and it isn't - I am still getting the same errors, so it is probably unlikely to be related to the Documents module.

Still, something somewhere on the site is trying to reference RadEditor and/or Telerik, despite them not being installed, as far as I can tell. I'll keep hunting, and as you suggested, I'll create a new Issue in GitHub.

FYI

Me too I had this error and I followed the 18 steps of the DNN Platform Telerik Removal guide.

To resolve the problem, I found under my Bin folder the DotNetNuke.RadEditorProvider.dll and I delete it.

That's it!

Posted By Sylvain Sanscartier on 5/11/2023 12:07 PM

To resolve the problem, I found under my Bin folder the DotNetNuke.RadEditorProvider.dll and I delete it.

Ah, yes... This is one of the steps.  So, it's very useful to double- and triple-check each step in the telerik removal documentation.  Until you've done it a few times in a row, there are minor things you might easily miss.  If you miss any telerik references of any kind, this is the situation you can expect to be in.  Thank you for this update!  :)  

 

Posted By exweeto on 3/31/2023 6:02 AM

Thanks for the feedback, Will.

I was able to upgrade the Documents module without any obvious problems, and most of the pages where the module was used were working properly. It was just one page where the Documents module was there and had a list of "documents", which was totally blank!

Anyway, I decided to remove the Documents module completely from the site, just to be sure that the RadEditor/Telerik error was not related, and it isn't - I am still getting the same errors, so it is probably unlikely to be related to the Documents module.

Still, something somewhere on the site is trying to reference RadEditor and/or Telerik, despite them not being installed, as far as I can tell. I'll keep hunting, and as you suggested, I'll create a new Issue in GitHub.

My next step would be to double- and triple-check the web.config and Bin folder.  Then, run through the telerik removal steps again, starting from the beginning.  It sounds like either something was missed, or you have a unique issue in your environment.  It would be difficult to tell, so far, but the issue in GitHub might help as well.