Per Nergård (MVP)
Jun 26, 2011
  4621
(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
Optimizely CMS 13: Why Search & Navigation Now Means Graph Migration

Optimizely CMS 13 makes Graph a required part of the platform. Here is what that means in practice for teams moving from Search & Navigation, with ...

Wojciech Seweryn | Apr 8, 2026 |

Jhoose Security Module V3.0.0 – Site-Level Security Configuration for Optimizely

Jhoose Security Module updated for Optimizely CMS 13, introducing separate packages for CMS 12 and 13 with ongoing support and enhancements.

Andrew Markham | Apr 6, 2026 |

Searchable settings page

In my current project which has been actively developed for quite some time we have a big classic settings page. Unfortunately the placement and...

Per Nergård (MVP) | Apr 6, 2026

Using Azure Devops Pipelines in Optimizely SAAS (Configured) Commerce

Introduction When working with SAAS Commerce build service v2 your currently need to use a github repo with configured branches to start deployment...

Mark Hall | Apr 4, 2026 |