[MGNLDATA-119] Tree with utf8 characters in its name can't be resolved properly Created: 24/Jan/11  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Magnolia Data Module (closed)
Component/s: None
Affects Version/s: 1.4.2
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Zdenek Skodik Assignee: Philipp Bärfuss
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File log.txt    
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

and throws the InvalidTreeHandlerException as attached.

To reproduce:

  • create a data type with utf8 chars
  • logout/login
  • follow to auto-created menu entry for the type


 Comments   
Comment by Federico Grilli [ 24/Jan/11 ]

the UnicodeNormalizationFilter seems to do its job and wraps the request with info.magnolia.cms.filters.UnicodeNormalizationRequestWrapper but then in info.magnolia.module.admininterface.AdminTreeMVCServlet.getHandler(HttpServletRequest, HttpServletResponse) the call to

String handlerName = request.getRequestURI();

returns the encoded URI instead of the normalized one.

Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 05:11:32 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.