Ben  McKernan
Dec 11, 2012
  11369
(2 votes)

Uncompressed JavaScript files for debugging EPiServer 7

Update: Click here for a guide on how to use uncompressed JavaScript files in EPiServer 7.6+

I’m not sure how many people are aware of the fact that there is actually a package containing the uncompressed versions of all the JavaScript files used in the new EPiServer 7 user interface available to be downloaded and used for debugging purposes.

In any case, we’ve just updated the download package to contain the RTM version of the files (since for the last few weeks it has been a CTP version). The download page can be found here:

http://world.episerver.com/Download/Items/EPiServer-CMS/EPiServer-7---CMS/EPiServer-CMS-Debugging-of-Client-Side-Files/

Installation Instructions

The package is a zip file which can be extracted directly into the root VPP folder for the site you wish to debug. All the files contained within the package have their filename suffixed with .uncompressed.js, meaning that they will not override the current compressed files. This allows you, as a developer, to switch between compressed and uncompressed files very simply.

Running with the Uncompressed Files

To tell the system to use the uncompressed files, simply add the following to the EPiServerFramework.config file underneath the episerver.framework element:

<clientResources debug="true" />

Happy coding!

Dec 11, 2012

Comments

Tore Gjerdrum
Tore Gjerdrum Nov 29, 2013 02:29 PM

Hi Ben,

Is it possible to get the uncompressed files for EPiServer CMS 7.1 as well?

Tore Gjerdrum
Tore Gjerdrum Dec 13, 2013 01:03 PM

Hi again,
Are these files also available for EPiServer 7.5 ?

Ben  McKernan
Ben McKernan Jan 17, 2014 04:05 PM

I believe it should be available via the add-on store.

Please login to comment.
Latest blogs
From Prompting to Production: Optimizely Opal University Cohort and the Future of Agentic MarTech

Most organizations today are still playing with AI. They experiment with prompts, test ideas in isolated chats, and occasionally automate a task or...

Augusto Davalos | Apr 28, 2026

Six Compelling Reasons for Upgrading to CMS 13

Most software updates ask you to keep up. Optimizely CMS 13 asks something different — it asks whether your digital strategy is built for a world...

Muhammad Talha | Apr 28, 2026

Optimizely CMS 13 breaking changes: GetContentTypePropertyDisplayName

When upgrading from CMS 12 to 13, resolving property display names may not work as before. Here’s what changed.

Tomas Hensrud Gulla | Apr 27, 2026 |

Accelerate Optimizely DAM Adoption: Unlocking Business Value with Metadata Bulk Import

Accelerating Optimizely DAM Adoption How a Metadata-Driven Bulk Import Utility Unlocks Real Business Value Executive Summary For enterprises runnin...

Vaibhav | Apr 27, 2026

Optimizely CMS 13 breaking changes: IValidate<T>

Custom IValidate validators in Optimizely CMS 13 are no longer auto-discovered. They must be registered explicitly when upgrading from CMS 12.

Tomas Hensrud Gulla | Apr 27, 2026 |