[MAGNOLIA-6330] Incorrect links for pages with UTF-8 names cause errors in the Page Editor Created: 31/Jul/15  Updated: 15/Apr/16  Resolved: 07/Aug/15

Status: Closed
Project: Magnolia
Component/s: page editor
Affects Version/s: 4.5.x
Fix Version/s: 4.5.26

Type: Bug Priority: Critical
Reporter: Lars Fischer Assignee: Federico Grilli
Resolution: Fixed Votes: 0
Labels: page-editor, support
Remaining Estimate: 0d
Time Spent: 1d
Original Estimate: Not Specified

Issue Links:
relation
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Sprint: Sprint 5 (Basel)
Story Points: 5

 Description   

See also the linked support tickets for more information.

To reproduce the problem:

  • set UTF-8=true in magnolia.properties
  • create a page with e. g. the name "caractères français" (you might choose the STK articles template)
  • open the page and put two componentes in the content area
  • try to move the second component to the first place
  • (first try does fail but does not give an error on the UI)
  • (second try generates an error)

It's also not possible to delete a component.

Investigation found that the error happens here:

InterceptFilter.java, line 209

Node parent = session.getNode(pathParent+srcName);

The path is wrong so fetching the node fails.

At the moment it seems the path is wrong from within the very first filter. This would mean the problems would the generated by paths/links generated in the PageEditor GWT code.

While fixing the issue we realised also adding a component or deleting it in page whose title contains UTF-8 characters would fail due to encoding issues with request parameters



 Comments   
Comment by Federico Grilli [ 03/Aug/15 ]

first move is okay but then a 404 error, as if the the characters are double-encoded or something

Generated at Mon Feb 12 04:13:29 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.