[DOCU-2772] Improve information about invalid characters Created: 12/Jul/23  Updated: 13/Jul/23  Resolved: 12/Jul/23

Status: Resolved
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Laura Delnevo Assignee: Laura Podkoritnik
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Documentation update required:
Yes
Epic Link: AuthorX improvements
Story Points: 1
Team: AuthorX
Approved:
Yes

 Description   

4. Certain special characters are only known to be prohibited for use after assets with such characters (e.g., “@”) are manually uploaded and causing the page not to render properly.
Provide a complete, updated list of prohibited special characters and keywords

Current documentation lists invalid characters "for Pages" https://docs.magnolia-cms.com/product-docs/6.2/Authoring/Managing-pages.html#_character_restrictions

  • Is it safe to assume that the list of invalid characters is also valid / the same for Assets?  
  • Do we have / can we compile a list of what’s possible or not when working with assets? Same list 

 

AC

Improve the documentation to make it more explicit how the invalid list of characters affects "nodes", not only Pages

Investigation Outcome

Magnolia uses a content repository to store any item, considering any web content (page), any asset, any configuration… Each item is stored as a Node in such content repo, and the node name is the key for access its properties.

So the Page restrictions can be extended also to the Assets, since both are stored in the same way into the repo, as Nodes.

There are 3 types/groups of restrictions to bear in mind:
1) Proper content repository restrictions. In this case, we are using the JCR JackRabbit (listed on the docu page)
2) Those characters which are not allowed to be part into any URL, specified also in the docu
3) Magnolia ones: “&”, “=“, “@“ 


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