Per Nergård (MVP)
Jun 26, 2011
  4639
(0 votes)

Hot to add validation of folder names in CMS5 filemanager

After migration of a CMS4 site we started to get a lot of reports of links that had stopped working.

I remembered that we had trouble with non allowed characters in an other site some time ago.

A quick check and sure enough we had a problem with “&” characters in some of the folder names.

In CMS 6 a validation has been added to avoid these problems but not in a default CMS 5 R2site.

Luckily there is an easy fix. Replacing the standard

<virtualPath customFileSummary="~/FileSummary.config" /> row in web.config with the below adds the validation.

<virtualPath customFileSummary="~/FileSummary.config"  illegalCharactersRegex="%|&amp;|\+|/COM[0-9]([/\.]|$)|/LPT[0-9]([/\.]|$)|/PRN([/\.]|$)|/CLOCK\$([/\.]|$)|/AUX([/\.]|$)|/NUL([/\.]|$)|/CON([/\.]|$)|/.+\.$" illegalCharactersDisplayString="%,&amp;,+,COM,LPT,PRN,CLOCK$,AUX,CON,NUL,*.">

I don’t understand why this functionality isn’t activated by default in  CMS5 and a recommendation to anyone upgrading a pre CMS5 site is to go through all the folders and correct any incorrect folder names.

Jun 26, 2011

Comments

Linus Ekström
Linus Ekström Jun 27, 2011 07:12 AM

@Per: The & character became restricted in one of the later IIS versions that has a default setting to not allow characters that can be decoded several times. That why we added the & character to the list of unwanted characters first in the CMS 6 version. There is even the posibility to allow the "&"-character. See the original form thread about the issue here: http://world.episerver.com/Modules/Forum/Pages/thread.aspx?id=34240

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