Brian Dukes wrote
If the changes that they suggest aren't limiting to those controls, you could suggest their inclusion in the DNN core (so that you won't have to mess with them again). You can add an issue at http://support.dotnetnuke.com and include that code, they are usually very good about getting good code included quickly in the next release or two.
Just a thought,
I could, but the RadEditor control is specifically designed for DotNetNuke. I would expect Telerik to take this up with the DotNetNuke team to get a resolution and it didn-t appear that the control had been fully tested against DNN releases otherwise they would have spotted this one.
If FCKeditor presented the same problem then I'd be clear where the problem had come from.
When I spend this amount of money, more than for any other module I've bought, then I really expect the provider to be extensively testing the product against beta releases of DNN.
brian wrote
What about turning off AJAX for those two core modules?
And yes if only two .ascx's need changed and not actual code.. why would you not do it?
I-m not sure if I could turn AJAX off - this is the user profile screen.
Yes, I could and would make the change if it was going to be followed up by a patch by the provider. The fact that I will have to make the same change to every future release of DNN is more of a concern - will this fix always work?
ROBAX
In general I found the control to be nearly as flexible as FCK and certainly supported file uploads and respected the DNN role security as far as I could see.