Localization in module template

[neilgallacher]

I was having trouble with localization in my Oqtane module with Radzen Blazor components.

At first I solved this by hardcoding the culture in ServerStartup which solved my problem but didn't seem a good solution as it was hard coded.

I eventually found that by changing the module ServerStartup to:

	public async void Configure(IApplicationBuilder app, IWebHostEnvironment env)
	{
		app.UseRequestLocalization();
	}

Localization (en-GB) was correctly applied to my module.

Having looked through the localization troubles in other older discussions I wondered if this modification became part of the module template it may save others time working out how to get localization working in their modules?

Of course there may be a better way?

[markdav-is]

The problem I'm having is that the lang picker always reverts to English. I'm looking for more conversations around this issue

[hishamco]

@markdav-is is this occur in the nightly build?

[sbwalker]

@markdav-is are you using the new Content Localization capability (10.1) or the legacy Languages capability? The Language Picker has 2 different behaviors depending on the configuration of your site.

[sbwalker]

@neilgallacher and @markdav-is I believe the behavior you are reporting is caused by the issue I just logged #6157

[markdav-is]

thanks for clarifying. it will be handy for our users to pick their default language as well as being able to switch between them.

[neilgallacher]

Thank you I will follow 6157