More in this section

Forums / Developing with Sitefinity / Custom Dialogs without the editor

Custom Dialogs without the editor

4 posts, 0 answered
  1. Bill
    Bill avatar
    15 posts
    Registered:
    04 Nov 2008
    10 Nov 2008
    Link to this post
    I have the sample code up an running for adding a custom dialog.
    My problem is that I don't need an editor on the calling page, just a plain old button. 
    I want to click a button and pass some XML to a custom dialog.  In the custom dialog I will populate a grid.  The user will then add or remove rows, I will modify the XML and return it to the calling screen.

    Is there a good example of how to do this?
  2. Pepi
    Pepi avatar
    981 posts
    Registered:
    31 Jan 2017
    11 Nov 2008
    Link to this post
    Hello Bill,

    I would recommend you use Telerik RadWindow control to achieve the required functionality. Please refer to the following online demo that provides a simple example how to open a window on demand, and execute a callback command that will perform some operation on the main page: Returning Values from a Dialog. Also, it might be helpful to investigate Using RadWindow as a Dialog topic that discusses RadWindow events and properties which you need to create dialogs.

    Do let us know if you need any further assistance.

    Regards,
    Pepi
    the Telerik team

    Check out Telerik Trainer, the state of the art learning tool for Telerik products.
  3. Bill
    Bill avatar
    15 posts
    Registered:
    04 Nov 2008
    11 Nov 2008
    Link to this post
    I tried this and it seems to be passing values back and forth.  One problem is that, in the modal window, if I click a command button in a grid I get an error that tells me to change my page settings to not validate...any ideas?

    A potentially dangerous Request.Form value was detected from the client (txtLocationsXML="...="utf-8"?><Locations><Location...").
    Description: Request Validation has detected a potentially dangerous client input value, and processing of the request has been aborted. This value may indicate an attempt to compromise the security of your application, such as a cross-site scripting attack. You can disable request validation by setting validateRequest=false in the Page directive or in the configuration section. However, it is strongly recommended that your application explicitly check all inputs in this case.
  4. Bill
    Bill avatar
    15 posts
    Registered:
    04 Nov 2008
    12 Nov 2008
    Link to this post
    Got it...thanks!
Register for webinar
4 posts, 0 answered