HomeDev GuideAPI Reference
Dev GuideAPI ReferenceUser GuideGitHubNuGetDev CommunitySubmit a ticketLog In
GitHubNuGetDev CommunitySubmit a ticket

Debug CMS UI

Describes how to debug the Optimizely Content Management System (CMS) user interface.

You can run your site with uncompressed JavaScript in edit view to debug the Optimizely Content Management System (CMS) user interface. To do this, you need to enable debug mode for client resources by adding <clientResources debug="true" /> to your web.config inside the episerver.framework element. You can then toggle the debug files on and off by changing the value of the debug attribute from true to false.

The CMS UI NuGet packages contain the JavaScript files required to run the user interface compressed into a zip file. The system then reads the contents of the zip file at run time. At initialization, if the client resources debug flag is set to true, the system first looks for a debug version of the JavaScript zip file and, if it exists, loads that instead.

The EPiServer.CMS.UI.Sources NuGet package contains original user interface source files together with uncompressed Dojo and Dijit.

Every release builds the source package, which ties into the continuous release cycle. You can install it the same way you would any other NuGet package from nuget.episerver.com.

Install-Package EPiServer.CMS.UI.Sources

If you need to manipulate sources files and then create a customized Dojo build you can use this package. It comes together with Dojo build tools.



To debug the CMS edit view, you do not need this package. The change described above is sufficient.