You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hi @Charles Focant,
Follow those instructions to add -Dfile.encoding=UTF8 parameter to your JVM startup
Hi @Charles Focant ,
as said by @Benjamin probably it is an issue due to db character encoding.
Please take a look to the following troubleshooting article https://confluence.atlassian.com/doc/troubleshooting-character-encodings-167194.html
HI @Charles Focant ,
Haven't encounter this issue during an upgrade. I'm wondering if there was a DB encoding issue. May want to check your troubleshooting and support page to wee if there's any fail checks.
It would be good to indicate what version you were upgrading from and to in case another member has gone through the same upgrade path.
7.18.3 -> 7.20.1 -> 8.01 ->8.02
So I'm currently at 8.0.2.
Please note that the accented characters show wrong only in the left column, not in the articles.
I don't see why there would be a problem in the database. I'm a junior sysadmin and have little knowledge about databases and Atlassian Products. I was hoping someone could help me.
It may have impacted it because the character may need to be change when upgrading.
Here's a documentation for further troubleshooting.
I followed the link to the test: /admin/encodingtest.action
The test succeeded.
What does it mean?
I have the impression it is not an issue with the database but with the iframe on the left side of the page.
Test 1: Raw text
This is the test string generated in Confluence
Test 2: Form submission
This is the test string pasted by you into the web form and submitted back to Confluence
Test 3: Database round-trip (select as lower-case)
This is the string from Test 2 after being stored in the database and then retrieved as lower-case
Expected result (converting Java string to lowercase)
Test 4: Database round-trip (select as upper-case)
This is the string from Test 2 after being stored in the database and then retrieved as upper-case
Expected result (converting Java string to uppercase)
Test 5: International file name support
Try to write a file to the confluence home directory with the test string as the file name
File was written successfully
Test 6: Detect international file name mangling
Detect whether the file system is mangling the file name when it is saved
The file name has been preserved
Thanks for the update. # of Agents are tied to the JSM product.
For confluence, is determine by the number of users tier. If you are on paid standard license for confluence server, you should be able to get support from Atlassian.
Here's the support link: