Release notes for Optimizely CMS and Customized Commerce updates

Hi Team,

Our client website is using signalr version 2.4.1 and this lead to conflict with Live monitor version 8.5.0 add on.

Please help us support Live monitor with latest signalr version (2.4.1)

Regards,

Steps to reproduce

1. Install LiveMonitorCommerce to QuickSilver site.
2. In the LiveMonitor.config file, set:
<monitoringTarget contentId="-2147483647__CatalogContent" />
(-2147483647__CatalogContent is id of Fashion catalog).

3. Open LiveMonitor in view mode.
4. A script error is displayed. Also, no node appears.

Steps to reproduce

1. Install a Commerce 12.x site.
2. Install LiveMonitor.Commerce.

Expected:
LIveMonitor.Commerce should compatible with Commerce 12x.

Actual:
Cannot install because it depends on Commerce.Core [11.5, 12.0).

CMS 11 support

When the site is hosted on CDN, the Live Monitor does not work and show the error:

System.FormatException: An invalid IP address was specified.
at System.Net.IPAddress.InternalParse(String ipString, Boolean tryParse)
at EPiServer.LiveMonitor.Services.CommonTracker.ProcessTrackingRequest(MonitoringData& monitoringData, HttpContextBase context)
at EPiServer.LiveMonitor.Controllers.TrackingController.Index()
at lambda_method(Closure , ControllerBase , Object[] )
at System.Web.Mvc.ReflectedActionDescriptor.Execute(ControllerContext controllerContext, IDictionary`2 parameters)
at System.Web.Mvc.ControllerActionInvoker.InvokeActionMethod(ControllerContext controllerContext, ActionDescriptor actionDescriptor, IDictionary`2 parameters)
at System.Web.Mvc.ControllerActionInvoker.<>c_DisplayClass15.<InvokeActionMethodWithFilters>b_12()
at System.Web.Mvc.ControllerActionInvoker.InvokeActionMethodFilter(IActionFilter filter, ActionExecutingContext preContext, Func`1 continuation)
at System.Web.Mvc.ControllerActionInvoker.InvokeActionMethodFilter(IActionFilter filter, ActionExecutingContext preContext, Func`1 continuation)
at System.Web.Mvc.ControllerActionInvoker.InvokeActionMethodFilter(IActionFilter filter, ActionExecutingContext preContext, Func`1 continuation)
at System.Web.Mvc.ControllerActionInvoker.InvokeAction(ControllerContext controllerContext, String actionName)
at System.Web.Mvc.Controller.ExecuteCore()
at System.Web.Mvc.ControllerBase.Execute(RequestContext requestContext)
at EPiServer.LiveMonitor.LiveMonitorMvcHandler.ProcessController(IController controller)
at EPiServer.LiveMonitor.LiveMonitorMvcHandler.BeginProcessRequest(HttpContextBase httpContext, AsyncCallback callback, Object state)
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

1. Install LIMO 8.4 on CMS.Core 10.9 pre-release MVC template
2. Add

<dependentAssembly>
<assemblyIdentity name="Microsoft.AspNet.SignalR.Core" publicKeyToken="31bf3856ad364e35" culture="neutral" />
<bindingRedirect oldVersion="0.0.0.0-2.0.3.0" newVersion="2.0.3.0" />
</dependentAssembly>

are added in web.config/<runtime><assemblyBinding
3. Change the optimizeCompilations="true" to optimizeCompilations="false" in web.config
4. Add
new EPiServer.LiveMonitor.Services.SignalR.LiveMonitorOWINStartup().Configuration(app);

in Startup.cs/public void Configuration(IAppBuilder app)

5. Build the project
6. Open the site
Actual: Missing "Login/Logout" link at the bottom of page
7. Navigate to Edit mode
Expected: Edit mode content is shown properly
Actual: Error is shown
Server Error in '/' Application.

Value cannot be null or empty.
Parameter name: linkText

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.ArgumentException: Value cannot be null or empty.
Parameter name: linkText

Source Error:

Line 23: @if(Model.Layout.LoggedIn)
Line 24: {
Line 25: @Html.ActionLink(Html.Translate("/footer/logout"), "Logout", new

)
Line 26: }
Line 27: else

Source File: c:\EPiServer\LIMO\LIMO\Views\Shared\Footer.cshtml Line: 25

Steps to reproduce

1. Install Live Monitor on a CMS/Commerce site.
2. Catalog1, Catalog2 is under Root.
3. User1 from Stockholm views Catalog1.
4. User2 from Hanoi views Catalog2.
5. Open CMS> Limo >Online/History visitor panel.

Expected:
Location=Region-Country of Location 1

Actual:
Location= Unknown

After installing LIMO addon with CMS 10.9.0 pre, error is thrown.
Server Error in '/' Application.
Value cannot be null or empty.
Parameter name: linkText
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.ArgumentException: Value cannot be null or empty.
Parameter name: linkText
Source Error:
Line 23: @if(Model.Layout.LoggedIn)
Line 24: {
Line 25: @Html.ActionLink(Html.Translate("/footer/logout"), "Logout", new

)
Line 26: }
Line 27: else
Source File: c:\EPiServer\LIMO\LIMO\Views\Shared\Footer.cshtml Line: 25

Steps to reproduce

1. Install Live Monitor (LiMo) on CMS/Commerce.
2. Open CMS > LiMo page.
3. Customize URL: http://site/EPiServer/EPiServer.LiveMonitor/Monitor?nodeids=<test>

Actual: error exception:
A potentially dangerous Request.QueryString value was detected from the client (nodeids="<test>").
Description: ASP.NET has detected data in the request that is potentially dangerous because it might include HTML markup or script. The data might represent an attempt to compromise the security of your application, such as a cross-site scripting attack. If this type of input is appropriate in your application, you can include code in a web page to explicitly allow it. For more information, see http://go.microsoft.com/fwlink/?LinkID=212874.

Exception Details: System.Web.HttpRequestValidationException: A potentially dangerous Request.QueryString value was detected from the client (nodeids="<test>").

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[HttpRequestValidationException (0x80004005): A potentially dangerous Request.QueryString value was detected from the client (nodeids="<test>").]
System.Web.HttpRequest.ValidateString(String value, String collectionKey, RequestValidationSource requestCollection) +9809768
System.Web.<>c_DisplayClass280_0.<ValidateHttpValueCollection>b_0(String key, String value) +22
System.Web.HttpValueCollection.EnsureKeyValidated(String key) +9807765
System.Web.HttpValueCollection.GetValues(String name) +17
System.Web.Mvc.ValueProviderResultPlaceholder.GetResultFromCollection(String key, NameValueCollection collection, CultureInfo culture) +20
System.Web.Mvc.NameValueCollectionValueProvider.GetValue(String key, Boolean skipValidation) +106
System.Web.Mvc.ValueProviderCollection.GetValue(String key, Boolean skipValidation) +89
System.Web.Mvc.DefaultModelBinder.BindModel(ControllerContext controllerContext, ModelBindingContext bindingContext) +264
System.Web.Mvc.ControllerActionInvoker.GetParameterValue(ControllerContext controllerContext, ParameterDescriptor parameterDescriptor) +331
System.Web.Mvc.ControllerActionInvoker.GetParameterValues(ControllerContext controllerContext, ActionDescriptor actionDescriptor) +105
System.Web.Mvc.ControllerActionInvoker.InvokeAction(ControllerContext controllerContext, String actionName) +522
System.Web.Mvc.Controller.ExecuteCore() +98
System.Web.Mvc.ControllerBase.Execute(RequestContext requestContext) +181
System.Web.Mvc.ControllerBase.System.Web.Mvc.IController.Execute(RequestContext requestContext) +10
EPiServer.Shell.Web.Mvc.ModuleMvcHandler.ProcessController(IController controller) +40
EPiServer.Shell.Web.Mvc.ModuleMvcHandler.BeginProcessRequest(HttpContextBase httpContext, AsyncCallback callback, Object state) +24
System.Web.Mvc.MvcHandler.BeginProcessRequest(HttpContext httpContext, AsyncCallback callback, Object state) +48
System.Web.Mvc.MvcHandler.System.Web.IHttpAsyncHandler.BeginProcessRequest(HttpContext context, AsyncCallback cb, Object extraData) +16
System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +103
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +155