User Localization settings

src/OrchardCore.Modules/OrchardCore.Users/Localization/Drivers/UserLocalizationDisplayDriver.cs

@@ -45,7 +45,7 @@ public override Task<IDisplayResult> EditAsync(UserLocalizationSettings section,
             // If Invariant Culture is installed as a supported culture we bind it to a different culture code than String.Empty.
             if (cultureList.Where(c => c.Value == "").Any())
             {
-                cultureList.Where(c => c.Value == "").FirstOrDefault().Value = Constants.Invariant;
+                cultureList.Where(c => c.Value == "").FirstOrDefault().Value = UserLocalizationConstants.Invariant;
             }
 
             model.SelectedCulture = section.Culture;

src/OrchardCore.Modules/OrchardCore.Users/Localization/Providers/UserLocalizationClaimsProvider.cs

@@ -28,7 +28,7 @@ public Task GenerateAsync(IUser user, ClaimsIdentity claims)
 
             if (localizationSetting.Culture != "none")
             {
-                claims.AddClaim(new Claim(CultureClaimType, localizationSetting.Culture == Constants.Invariant ? "" : localizationSetting.Culture));
+                claims.AddClaim(new Claim(CultureClaimType, localizationSetting.Culture == UserLocalizationConstants.Invariant ? "" : localizationSetting.Culture));
             }
         }
 

src/OrchardCore.Modules/OrchardCore.Users/Localization/Providers/UserLocalizationRequestCultureProvider.cs

@@ -24,6 +24,6 @@ public override Task<ProviderCultureResult> DetermineProviderCultureResult(HttpC
             return NullProviderCultureResult;
         }
 
-        return Task.FromResult(new ProviderCultureResult(userCulture == Constants.Invariant ? "" : userCulture));
+        return Task.FromResult(new ProviderCultureResult(userCulture == UserLocalizationConstants.Invariant ? "" : userCulture));
     }
 }

src/OrchardCore.Modules/OrchardCore.Users/Localization/Constants.cs → src/OrchardCore.Modules/OrchardCore.Users/Localization/UserLocalizationConstants.cs

@@ -1,6 +1,6 @@
 namespace OrchardCore.Users.Localization
 {
-    public static class Constants
+    public static class UserLocalizationConstants
     {
         public const string Invariant = "invariant";
     }

src/docs/reference/modules/Users/README.md

@@ -15,11 +15,16 @@ The module contains the following features apart from the base feature:
 - Two-Factor Authentication Services: Provices Two-factor core services. This feature cannot be manually enabled or disable as it is enabled by dependency on demand.
 - Two-Factor Email Method: Allows users to two-factor authenticate using an email.
 - Two-Factor Authenticator App Method: Allows users to two-factor authenticate using any Authenticator App.
+- User Localization: Allows ability to configure user culture per user from admin UI.
 
 ## Two-factor Authentication
 
 Starting with version 1.7, OrchardCore is shipped with everything you need to secure your app with two-factor authentication. To use two-factor authentication, simply enable "Two-Factor Email Method" and/or "Two-Factor Authenticator App Method" features. You can configure the process based on your need by navigating to `Security` >> `Settings` >> `User Login`. Click on the "Two-Factor Authentication" tab and update the settings as needed.
 
+## User Localization
+
+This feature adds a `RequestCultureProvider` that will retrieve the current user culture from it's claims. This feature will set a new user claim with a `CultureClaimType` named "culture". The feature adds the ability to configure the culture per user from the admin UI. It also have a culture option to fallback to other ASP.NET Request Culture Providers by simply setting the user culture to "Use site's culture" which will also be the selected default value.
+
 ## Custom Paths
 
 If you want to specify custom paths to access the authentication related urls, you can change them by using this option in the appsettings.json:

src/docs/releases/1.9.0.md

@@ -153,7 +153,26 @@ public class AdminMenu : INavigationProvider
 }
 ```
 
+### Admin Routes
+
+The `[Admin]` attribute now has optional parameters for a custom route template and route name. It works just like the `[Route(template, name)]` attribute, except it prepends the configured admin prefix. You can apply it to the controller or the action; if both are specified then the action's template takes precedence. The route name can contain `{area}`, `{controller}`, and `{action}`, which are substituted during mapping so the names can be unique for each action. This means you don't have to define these admin routes in your module's `Startup` class anymore, but that option is still available and supported. Take a look at this example:
+
+```csharp
+[Admin("Person/{action}/{id?}", "Person{action}")]
+public class PersonController : Controller
+{
+    [Admin("Person", "Person")]
+    public IActionResult Index() { ... }
+
+    public IActionResult Create() { ... }
+
+    public IActionResult Edit(string id) { ... }
+}
+```
+
+In this example, (if the admin prefix remains the default "Admin") you can reach the Index action at `~/Admin/Person` (or by the route name `Person`), because its own action-level attribute took precedence. You can reach Create at `~/Admin/Person/Create` (route name `PersonCreate`) and Edit for the person whose identifier string is "john-doe" at `~/Admin/Person/john-doe` (route name `PersonEdit`).
+
 ## Users Module
 
-Added new user localization feature that allows to set default culture per user in the admin UI.
+Added a new User Localization feature that allows to be able to configure the culture per user from the admin UI.