IMPORTANT: This version of Sitefinity CMS is out of support and the respective product documentation is no longer maintained and can be outdated. Use the version selector to view a supported product version.
When you work with widgets and open a widget designer or click on a command inside a RadDock, by default the designer or command window are displayed in as RadWindow. With Sitefinity CMS, you can use a new, lighter JavaScript-based window. By default, widget designers use a Bootstrap window. You can, however, customize the windows and you can have a different user interface control to wrap the designer.
This is possible because a Sitefinity CMS script handles the logic for rendering the content of the designer, including the designer script. The script puts the content inside the body of the page, so that the content is displayed upon clicking Edit. Once you create your custom widget designer window, it is important to trigger the modalDialogClosed event when the dialog is closed, so the markup of the dialog is removed from your page.
modalDialogClosed
NOTE: When you trigger the modalDialogClosed event, make sure to use $telerik.$ instead of just $ or any other jQuery global variable. You do this because third party widget designers may load another jQuery instance and replace the global variables, making the trigger useless since the binding was on the previous jQuery instance.
$telerik.$
$
To customize the widget designer window of a ContentBlock widget to use a Kendo window:
Designer.cshtml
As a result, you can see the new Kendo window of the widget designer.
Back To Top
To submit feedback, please update your cookie settings and allow the usage of Functional cookies.
Your feedback about this content is important