Ben  McKernan
Dec 11, 2012
visibility 11553
star star star star star
(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.

error Please login to comment.
Latest blogs
Finding Thomas Part 3 - The Moment of Recognition

Remember Thomas? In digital landscape, Thomas is the returning visitor who reads everything, opens every email, converts on nothing. In standard...

Ritu Madan | Jun 26, 2026

Add more scheduled job settings from the Optimizely CMS 12 admin UI -- with OptiScheduledJob.ExtraParameters

  Optimizely (EPiServer) CMS 12 ships a great scheduled-jobs framework, but it has one frustrating gap: a job has nowhere to store its own...

Binh Nguyen Thi | Jun 25, 2026

Automated Search & Navigation to Graph Migration with Claude Code

A Claude Code plugin that scans your S&N codebase, applies Graph SDK transformations, and validates the result. Install once, run one command. CMS ...

Connor Fortin | Jun 24, 2026

Migrating from Find to Graph: Lessons Learned from a Real CMS 13 Project

While migrating a search solution from Optimizely Search & Navigation (Find) to Optimizely Graph in CMS 13, I encountered several issues that were...

Binh Nguyen Thi | Jun 24, 2026

Optimizely: Upgrade Opti-ID and .NET 10 in CMS 12

Many Optimizely customers are planning their roadmap around a future migration to Optimizely CMS 13. As a result, upgrades such as Opti ID adoption...

Madhu | Jun 23, 2026 |

Understanding Optimizely Graph: Caching, Webhooks & Avoiding Stale Content (Optimizely SaaS CMS)

📌 Scope: This post covers Optimizely CMS (SaaS) only — using the official @optimizely/cms-sdk and @optimizely/cms-cli packages with Next.js 15. If...

Kiran Patil | Jun 23, 2026 |