Hi All

Given that this issue has been around now for a year and that it's only a minor issue with very few votes I'm going to close this one out as won't fix as I feel it better reflect the true status of this issue. Should this be raised again in the future we'll reconsider this.

Regards
Steve Haffenden
Confluence Bugmaster
Atlassian

moving all PDL issues in 5.1 to 5.2 for now so that we can move back in the ones we plan to fix.

As discussed, given:

this bug would only show up when you're installing Confluence with a language other than your system locale, e.g. Confluence set to German on a machine with an English system locale. And, again, this only happens during setup

and

Reproduced the exact same behavior, down to the mixed-language success screen, in Confluence 4.3.6 and 3.5.11.

Reproduced the exact same behavior, down to the mixed-language success screen, in Confluence 4.3.6 and 3.5.11.

Further findings:

1. This odd behavior is caused by the interplay of LanguageExtractionFilter and the classes implementing LocaleManager.
2. One of the (many) data-sources looked at when determining language is the system locale. That is where the English is coming from in my case.

It appears this bug would only show up when you're installing Confluence with a language other than your system locale, e.g. Confluence set to German on a machine with an English system locale. And, again, this only happens during setup. Reprioritize?

I've investigated this further. Here are my findings:

1. If you switch to German on the license screen (setuplicense), then that screen and the ones related to setting up the database (setupdb-start, setupstandarddb-start, setupdatasourcedb-start) will be entirely in German.
2. The screens related to setting up data (setupdata-start, setup-restore-start) and user management (setupusermanagementchoice-start, setupadministrator-start, connecttojira-start) will be entirely in English.
3. The success screen (finishsetup) will have German chrome (header, footer) but English content.

A few good leads:

1. Confluence switches Spring context, from setup to main, between the database-setup and data-setup steps. This is a prime candidate for an underlying cause for this bug.
2. com.atlassian.config.bootstrap.DefaultAtlassianBootstrapManager#isSetupComplete starts returning true at finishsetup. Also, see com.atlassian.confluence.web.filter.LanguageExtractionFilter#getLocaleManager. Conspicuous.