November Happy Hour will be moved to Thursday December 5th.
This topic lists Optimizely updates, delivered as NuGet packages and services. You decide which updates apply to your project.
Select a product, package, or service in the left menu, and then select one of the following filters from Item type and click Filter.
Note: NuGet packages listed here may not be immediately available in the Optimizely NuGet feed.
Latest changes
Fixed an issue that prevented the loading of an object as a PropertyBag. This issue occurred when a type with an enum property was stored in DDS and then later was no longer present. The missing missing enum value should have returned as an int but the load failed System.ArgumentNullException: Value cannot be null. (Parameter 'key').
Fixed an issue that redirected you to an existing URL even when you entered a non-existent URL (which should produce an HTTP 404).
Fixed an issue where the ViewBag properties were empty in block views, even though it was populated with custom ViewData.
Fixed an issue with IContentUrlGeneratorEvents interface where both GeneratingUrl and GeneratedUrl did not contain URL query string information.
Fixed an issue with a secondary exception in DefaultDataExporter.Export which caused code cleanup to occur before logging the issue. The code cleanup could result in an error, and no issue would be logged. Now, the issue is logged before code cleanup starts.
Fixed an issue where UIHintModelTemplateTagProvider loaded custom attributes of the property and slowed down performance.
Fixed an issue where PropertyLinkItem and PropertyXhtmlString needed to be marked as modified to get persisted.
Fixed an issue where ScheduleJobBase.OnStatusChanged threw an exception when a message longer than 2048 characters was entered. Now, if a longer message is entered, it is truncated to 2048 characters.
Fixed an issue where a regular expression used for validating links was created in an inefficient way and unnecessarily increased the duration of the job.
Fixed an issue where incorrectly formatted URLs in TinyMCE caused UI to not load for that content. Now, the link works by filtering out incorrectly formatted URL parameters or by treating the link as external if something goes wrong while resolving the internal content.
