-
Bug
-
Resolution: Fixed
-
Low
-
4.2.8
-
Standalone Confluence, JDK1.6, CentOS
Hello,
yesterday I posted this issue on Atlassian Answers, but I feel it really might be a bug, so I'm reporting it also here.
It's a problem with Confluence JSON-RPC API, "getChildren" method.
In the API output, Confluence pages titles containing "special characters" are not encoded correctly. See example:
[
{
"version": 1,
"parentId": 28148060,
"permissions": 0,
"id": 28835879,
"space": "TEST",
"title": "Copy of Will s��",
"url": "https://confluence:8443/pages/viewpage.action?pageId=28835879"
},
{
"version": 1,
"parentId": 28148060,
"permissions": 0,
"id": 29753574,
"space": "TEST",
"title": "Special chars-�??�?�?b��",
"url": "https://confluence:8443/pages/viewpage.action?pageId=29753574"
},
{
"version": 3,
"parentId": 28148060,
"permissions": 0,
"id": 28835875,
"space": "TEST",
"title": "Will s��",
"url": "https://confluence:8443/pages/viewpage.action?pageId=28835875"
}
]
No matter what HTTP header I setup, it doesn't correct the output.
![[Extranet] Page](/images/icons/generic_link_16.png "[Extranet] Page"){kind=icon}
[CONFSERVER-29755] Problem with text encoding for output from getChildren JSON-RPC API in Confluence
Please update the priority of this issue to at least Critical. It is basically a non-starter/Blocker for any users using non-ANSII characters.
Thank you for the information and response. Will you be updating this ticket when it is completely rolled out to the Confluence Cloud/Connect platform? Or is there somewhere else to watch? Until then our AddOns won't work for any customers using international characters.
Brendan
Hi Brendan and Thiago,
Thanks to Matt, the fix has been merged to confluence-json-rpc-plugin repository. We still need to release a new version of that plugin and perform some testing before updating the plugin in Confluence. This work is on our backlog but there are a number of higher priority issues that we need to address before this. As soon as we have an more information on this issue we'll update this ticket with details.
Regards
Olli Nevalainen
Confluence Bugmaster
Atlassian
Thiago Rossato
added a comment - Hi, we are having problems with Copy Space and Copy Page Tree plugin because of this issue. We are from Brazil and it is impossible to live without special characters like ç, ã, á, é, ó, ê, etc.
I'm paying for Confluence On Demand (for 500 users) and plugins support and need to know when it is going to be fixed for On Demand instances. Otherwise I have no reason to keep paying for the plugins (they are not fully functional) and I'll want ask for my money back.
Thiago Rossato
added a comment - Hi, we are having problems with Copy Space and Copy Page Tree plugin because of this issue. We are from Brazil and it is impossible to live without special characters like ç, ã, á, é, ó, ê, etc.
I'm paying for Confluence On Demand (for 500 users) and plugins support and need to know when it is going to be fixed for On Demand instances. Otherwise I have no reason to keep paying for the plugins (they are not fully functional) and I'll want ask for my money back. It looks like the pull request was merged but I'm not sure how to tell when it will be deployed. Does anyone know how to tell when such a merge will be deployed? And is this also what's being used by "Cloud" servers? I'd assume so.
A pull request for this issue has been submitted:
The changes set the character encoding to UTF-8 (previously it was setting the encoding to ISO-8859-1).
The JSON-RPC plugin apparently is i18n-ignorant – https://bitbucket.org/cmiller_atlassian/confluence-json-rpc-plugin/issue/15/chinese-words-encoding-problem-with-json
Wow! Thanks! When will this go live to Confluence Cloud?