Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Telerik, DNN & AjaxTelerik, DNN & Ajax
Previous
 
Next
New Post
1/22/2008 11:26 AM
 

I've spent the last 10 days trying to integrate RadEditor into DNN as a replacement for  FCKEditor.  I experienced a few problems with the configuration and these were resolved successfully and promptly by the support team.

The last problem has proved a job stopper.  I'm running DNN 4.8.0 with Ajax enabled (as a host setting).  When I access the user profile (clicking on the registered user name) the user bio section crashes with an error message raised by the editor component.

When I reported the problem to support I was presented with a comprehensive answer as to the changes I would have to make in the DNN core to rectify the issue, applying changes to users.ascx and profile.ascx.

OK, as a temporary fix that might be a solution and I'm not that adverse to rolling my sleeves and fiddling.  When it comes to security components, then I'm less happy and suggested to support that a patch to the editor should be forthcoming.

To my surprise the response from the lead developer was:-

2. In your scenario, however, it is no ordinary case - because MS AJAX is used. MS AJAX is neither part of DNN, nor of Telerik. It is a technology provided by Microsoft. When 3 technologies from three different vendors are combined, it is only common that additional "glue" might be needed. This is not something unusual - despite the fact that each vendor has made their best to make the technology as flexible as possible.

3. We have explained to you where the problem comes from (inherent MS AJAX limitation), and how to workaround it. It is not possible for us to do more than that - further notice about the problem should be delivered to Microsoft's MS AJAX team.

I won't be getting on to Microsoft about the problem just yet, but if any of MS team are listening in - perhaps you'd like to install a fix.

He also offered a full refund and reluctantly I think that's my only practical option.  I just don't see modifying DNN core components for every future upgrade (and they come thick and fast with DNN) is going to be a way forward for me and I get worried when my component vendor starts pointing the finger at other parties.

 
New Post
1/22/2008 11:57 AM
 

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,


Brian Dukes
Engage Software
St. Louis, MO
866-907-4002
DNN partner specializing in custom, enterprise DNN development.
 
New Post
1/22/2008 12:22 PM
 

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?

 
New Post
1/22/2008 6:25 PM
 

I'm very interested in the results of this as I've been considering implementing RAD as well lately; mainly for the purpose of gaining the image processing abilities that it appears to have, and so long as it integrates fully with the DNN file system and permissions like FCK does.. and then of course there is whether or not it does internal portal links like FCK.. and does it let one delete images or files off the file system through its own dialogues? I have loads of questions about that, but more inportant right now is of course whether your problem can be easily sorted. I fully agree that it's a problem when vendors point the finger elsewhere.. it's not a good omen, and is far too common with developers.

What sort of changes are required to the users and profile pages... if it's just something minor and isn't going to get worse over time, then it's probably ok.

I have a list of about 30 core files and dozens of graphics that I check through each DNN upgrade and it's not really a problem so long as you have good records and procedures... and use Winmerge to see what, if anything, has changed to those files each time.

Let us know what happens

Rob

 
New Post
1/22/2008 11:22 PM
 

Hi,

I've tried to implement the RADeditor and I've found that the FCK has better security implementation.  There are configuraitons where you can set folder permissions tied to the user role.  In my case that wouldn't work because I need to have a user role to have access to a department folder.  And the way Telerik has implemented their security, their would be a specific folder for the user within the department folder.  They do say you could give the user read/write access to every folder, but it's an all or nothing implementation with no granular security abilities like the FCK editor has.  I don't want users from one department to be able delete/edit files from another departmetn.

It's a gread editor, but until they can mimic the FCK security, I'm going to have to hold off.

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Telerik, DNN & AjaxTelerik, DNN & Ajax


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out