After some more testing it was found that the solution above breaks anchor links. I added a check for the anchor box below. This all goes in the same place (line 49)
//linkUrlTextBox.value = obj.get_value();
                    var linkAnchorSelect = document.getElementById("ExistingAnchor");
                    if (linkAnchorSelect.selectedIndex == 0){
                        var url = obj.get_value();
                        var remove = window.location.protocol + '//' + window.location.host;
                        linkUrlTextBox.value = url.replace(remove, '');
                    }

I'm not sure since I haven't downloaded it.

I'm finding more and more issues with the radEditor that I may just switch back to FCK. I seem to have a lot of issues with the editor spacing elements and wrapping classes incorrectly. Another big issue is that it removes what it thinks are unnecessary line breaks or inserts paragraphs without a non-breaking space. It makes using the editor a total crapshoot for a novice content manager. Another great example of a half baked implementation, implemented by developers with little UX testing. Most of the issues are from the DNN implementation of the RE. Before it was included, the provider from telerik was much, much better.

There is an offshoot RE provider on codeplex that promises a lot, but I haven't tried it yet.

If you would like these issues to be fixed - please log each issue in support.dotnetnuke.com. Please give the FULL detail of each problem (one per issue). If there is a code please state it (it will speed things up). Much appreciateed.

---

---

---