[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jan Haderka reopened MAGNOLIA-3233:
-----------------------------------


Committed fix breaks activation when public instance has 
{{magnolia.utf8.enabled=false}} or when public instance is older version before 
this feature have been introduced.
The fix should check the value on the author and encode all headers only when 
UTF8 support is enabled on the author instance.


> error on activate recursively a content with utf8 enabled and parent node 
> composed by special chars (ex. "/fòò/bàr")
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: MAGNOLIA-3233
>                 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3233
>             Project: Magnolia
>          Issue Type: Bug
>          Components: activation
>    Affects Versions: 4.3.1, 4.3.2
>            Reporter: Luca Boati
>            Assignee: Luca Boati
>             Fix For: 4.3.3, 5.0
>
>
> magnolia.uft8.enabled = true
> handle /fòò/bàr
> activating recursively "/fòò" or activating "bàr" node
> I got this error:
> "Message received from subscriber: Activation failed | /fòò on localhost"
> solution proposed:
> - encoding message header request or at least parentPath key
> parentPath = URLEncoder.encode(parentPath, "UTF-8");
> SimpleSyndicator.java and BaseSyndicatorImpl.java
> - decoding header, inside UnicodeNormalizerRequestWrapper.java

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to