cancel
Showing results for 
Search instead for 
Did you mean: 

Ampersands in filenames

marcus
Champ in-the-making
Champ in-the-making
In 1.4 preview, I could create a document with an ampersand in its name. However, with 1.4rc1 I'm getting the following

Constraint: Value 'Communicate &amp;Consult' matches regular expression: .*[\"\*\\\>\<\?\/\:\|\xA3\xAC\%\&\+\;]+.*

Why is it that ampersands are no longer allowed in document names? Ideally I'd like documents with all allowable Windows based filenames as that's what my end users are comfortable with (and the several thousand documents with ampersands in their name already Smiley Wink).
3 REPLIES 3

derek
Star Contributor
Star Contributor
Hi,

http://issues.alfresco.com/browse/AR-194
http://wiki.alfresco.com/wiki/Constraints

The various clients enforce these constraints, leaving the repository able to support only the common set.  You may find that the previous versions of Alfresco generated loads of WARN messages instead of disallowing the name.  You can go back to that if you wish:  See the integrityChecker bean in node-services-context.xml.

A better alternative, if you're absolutely sure that you don't want to support the other clients ever again, is to relax the constraint cm:name as defined in contentModel.xml.

Regards

marcus
Champ in-the-making
Champ in-the-making
Thought as much, I'll modify the constraint accordingly.

marcus
Champ in-the-making
Champ in-the-making
After giving it a shot, it seems that /alfresco/scripts/validation.js has the same regex pattern in it that needed to be modified