* Adds a new CultureSelector shape for front-end
* fixed query string culture change
* Moving NameValueCollectionExtensions from Orchard.DynamicForms and Orchard.Localization to Orchard.Framework
* Code styling
* Simplifying UserCultureSelectorController and removing the addition of the culture to the query string
* EOF empty lines and code styling
* Fixing that the main Orchard.Localization should depend on Orchard.Autoroute
* Code styling in LocalizationService
* Updating LocalizationService to not have to use IEnumerable.Single
* Matching culture name matching in LocalizationService culture- and casing-invariant
---------
Co-authored-by: Sergio Navarro <jersio@hotmail.com>
Co-authored-by: psp589 <pablosanchez589@gmail.com>
* Add Excel Export functionality to DynamicForms.
* Using the net46-targeted DLL of DocumentFormat.OpenXml instead of net40
* Updating DocumentFormat.OpenXml to latest (3.0.2) version
* Code styling
---------
Co-authored-by: Benedek Farkas <benedek.farkas@lombiq.com>
ModelBinding failed due to the "null" key being specified. Instead, the type name of the model should be specified as the key (which happens by default when no key is specified). Not sure how this worked before, since this code has been there from the beginning, and file histories don;t show an obvious change. Perhaps due to the upgrade to newer ASP.NET MVC?
The issue was that if you first "new up" a content item, update its content fields, and then invoke "create", its version record will be created, effectively wiping out the content fields' state.
Since we already know we want to create the content item, we can new up the content item and go ahead and create its version record, deferring event handlers from being triggered when we would start out with "Create".
