[MGNLSTK-393] Search form encoding issue Created: 09/Jun/09  Updated: 23/Jan/13  Resolved: 06/Aug/09

Status: Closed
Project: Magnolia Standard Templating Kit (closed)
Component/s: None
Affects Version/s: None
Fix Version/s: 1.1.2

Type: Bug Priority: Major
Reporter: Magnolia International Assignee: Teresa Miyar
Resolution: Workaround exists Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
relation
is related to MAGNOLIA-2835 Configure bundled Tomcat to use UTF-8... Closed
is related to MGNLEE-154 Configure bundled Tomcat to use UTF-8... Closed
Template:
Acceptance criteria:
Empty

 Description   

A workaround would be to use the POST form method, but that's not exactly satisfying.
Managing the encoding in the model could also work, but I really think it should be solvable at template/form/container level.
There was an issue before with the old Magnolia samples where we found out quite a few things about this, can't find it right now.



 Comments   
Comment by Magnolia International [ 09/Jun/09 ]

MAGNOLIA-630 and MAGNOLIA-1512 are slightly related.

Comment by Magnolia International [ 09/Jun/09 ]

See http://confluence.magnolia-cms.com/display/DEV/URI+encoding+in+Tomcat for some draft notes.

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