Thread Culture

Topics: Core, Localization
Apr 21, 2015 at 6:45 PM
On displaying or editing non-integer numbers (decimal, single and double) Orchard is using hosting system culture instead of site culture.

It's quite easy to get around for display but TryUpdateModel method don't care about site localization. Using same code and same site localization on different hosting environments produces different results.

Shouldn't we set thread culture for each request ?
Apr 21, 2015 at 6:46 PM
Often thought the same, can you raise a bug on Github please?
Apr 21, 2015 at 6:57 PM
Issue opened here