Hi!
We're encountering two related issues in our Confluence 9.2 Data-center , specifically involving pages with Cyrillic (non-Latin) titles.
{Include Page}
macro fails for Cyrillic-titled pagesWhen using the “Include Page” macro via the editor (+ → Other macros → Include Page
) and selecting a page with a Cyrillic title such as:
Отладочная страница
…the macro fails to render with the following message during preview and after publishing:
Unable to render {include} The included page could not be found.
The page exists, has a valid URL, and is accessible directly. There are no restrictions on the page. However, when the page title is changed to Latin characters (e.g., TestPage
), the macro works correctly.
createpage.action
When we paste a full link like:
…it is automatically rewritten into:
This leads to the “Create Page” screen, even though the linked page exists. This confuses users and may result in accidental creation of duplicate pages.
Interestingly, if we rename the page to use only Latin characters (e.g. TestPage
) or even just change the first character of the title to a Latin letter, the link resolves correctly and is no longer redirected to createpage.action
.
Is this a known issue in Confluence 9.x?
Are there any workarounds to ensure that:
Include Page
works with non-Latin titles?
Smart Links don’t rewrite valid URLs into createpage.action links?
Thank you in advance for your assistance.
Best regards,
Max
I wasn't able to locate any recent bug reports of this nature. However if the setup database for an on premise edition of Confluence did not set the character encoding to use a UTF8, I could see how problems like this might occur. I'd recommend checking out https://confluence.atlassian.com/doc/configuring-database-character-encoding-177698.html and https://confluence.atlassian.com/doc/troubleshooting-character-encodings-167194.html as next step guides to try to resolve this problem.
Hi @Max_admin ,
There are some bugs related to Cyrillic characters, but I can't find anything related to your description.
I've asked someone from Atlassian to take a look at this question so I guess they'll get back to you here. As I currently don't have any DC environment running, I can't try to search for any possible workarounds.
Hopefully, the support team can give some additional insights.
Cheers,
Tobi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.