This is a migrated thread and some comments may be shown as answers.

Feature Request: DialogHandler in web.config as axd by Default

3 Answers 109 Views
Editor
This is a migrated thread and some comments may be shown as answers.
Chase Florell
Top achievements
Rank 1
Chase Florell asked on 22 Mar 2009, 11:01 PM
I am in the process of developing an app that uses URL Rewriting and I just came up against a small issue where as the RadEditor registers the Telerik.Web.UI.DialogHandler as an ASPX.  The problems comes with the fact that I am rewriting *.aspx to go to Default.aspx?slug=*

I would simply like to suggest that the DialogHandler be registered as an axd by default (This would save from having to set the DialogHandler property in every instance of the RadEditor)

3 Answers, 1 is accepted

Sort by
0
Lini
Telerik team
answered on 24 Mar 2009, 10:38 AM
Hello,

We plan to change the default name of the editor dialog handler to .axd in the next release.

You can easily change it in the current version by doing the following two steps:

1) open the web.config file and replace Telerik.Web.UI.DialogHandler.aspx with Telerik.Web.UI.DialogHandler.axd
2) set the RadEditor's DialogHandlerUrl property to "~/Telerik.Web.UI.DialogHandler.axd"

All the best,
Lini
the Telerik team

Check out Telerik Trainer , the state of the art learning tool for Telerik products.
0
Chase Florell
Top achievements
Rank 1
answered on 27 Mar 2009, 02:18 AM
I have actually set it in a .skin file to override ALL editors on the site... I just wanted to post a suggestion that it be changed by default since it a) doesnt HAVE to be a .aspx and b) re-writing is popular enough that its a small problem that can be annoying if you don't figure it out right away.

Would just be nice to have .axd a standard for ALL handlers.
0
Tervel
Telerik team
answered on 30 Mar 2009, 12:07 PM
Hello Chase,

You are absolutely correct - however we need to also take care of keeping backwards compatibility and making upgrade as seamless as possible. Since the release of the RadControls for ASP.NET AJAX we have largely been able to keep backward compatibility of the server and client API's (with very few exceptions made for good reasons). As of Q1 2009 release we have also streamlined the skinning conventions for all RadControls - so in the future custom skins should contine to function with upgrades as well.

To further facilitate the upgrade process we are now working on an project upgrade tool which should appear with the next major RadControls release. In fact, we had made the aforementioned change from .aspx to .axd, but we reverted it back for this very reason.

All the best,
Tervel
the Telerik team

Check out Telerik Trainer , the state of the art learning tool for Telerik products.
Tags
Editor
Asked by
Chase Florell
Top achievements
Rank 1
Answers by
Lini
Telerik team
Chase Florell
Top achievements
Rank 1
Tervel
Telerik team
Share this question
or