[DOCU-239] Full stop character allowed in node names Created: 22/Dec/11  Updated: 03/Nov/15

Status: Closed
Project: Documentation
Component/s: content
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Antti Hietala Assignee: Antti Hietala
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:

 Description   

Starting with 4.5, the full stop character (en-us "period", Unicode 002E, UTF8 2E) is allowed in node names. Root cause for this change was the need to store binary files in the resources workspace. Theme resources (CSS, JavaScript, images) can now be stored in the same workspace as the rest of theme configuration. Any resource file name that has full stops is OK, e.g. flowplayer-3.2.7. The change is not limited to resources - all workspaces now support the full stop character in node names.

Examples (hypothetical):

  • User john.smith
  • Javascript jquery.tabtree
  • Document Magnolia-Flyer-4.0.pdf

To do: Change documentation where disallowed characters are discussed, removing full stop. Create a list of disallowed characters in one place and reference it from elsewhere.

Characters are validated in info.magnolia.cms.core.Path. See getValidatedLabel and isCharValid methods.

In principle, Magnolia allows you to use the UTF-8 character set in node names. However, some characters are invalid.

JCR 2.0 specification defines the following invalid characters in a local name:

  • Space, UTF-8 20
  • / Solidus (forward slash), UTF-8 2F
  • : Colon, UTF-8 3A
  • [ Left square bracket, UTF-8 5B
  • ] Right square bracket, UTF-8 5D
  • | Vertical line (pipe), UTF-8 7C
  • * Asterisk, UTF-8 2A

Node names can also be present in a URL. Therefore, they cannot contain characters that are not allowed in URLs or have a special meaning in a URL. http://www.ietf.org/rfc/rfc1738.txt

  • ; Semicolon, UTF-8 3B
  • / Solidus (forward slash), UTF-8 2F
  • ? Question mark, UTF-8 3F
  • + Plus sign, UTF-8 2B
  • % Percent sign, UTF-8 25
  • ! Exclamation mark, UTF-8 21
  • # Number sign (pound, hash), UTF-8 23
  • ^ Circumflex access, UTF-8 5E

Additional invalid characters in Magnolia CMS:

  • @ Commercial at, UTF-8 40
  • & Ampersand, UTF-8 26
  • = Equals sign, UTF-8 3D


 Comments   
Comment by Antti Hietala [ 23/Dec/11 ]

Important! Node name cannot start with full stop. The character is only allowed inside the string or at the end.

Comment by Richard Unger [ 23/Dec/11 ]

IMHO it would not hurt to allow '@' in node-names.

This would be useful for the users workspace, where usernames could then be identical to email adresses.

Comment by Ruth Stocks [ 27/Jan/12 ]

Content added to - http://docuauthor.magnolia-cms.com/editing/actions.html#Characterrestrictions.

Comment by Antti Hietala [ 30/Jan/12 ]

Published at http://documentation.magnolia-cms.com/editing/actions.html#Characterrestrictions

Generated at Mon Feb 12 01:07:15 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.