Blog posts by Per Nilsson

Blog posts by Per Nilsson2016-04-13T14:25:43.6000000Zhttps://world.optimizely.com/blogs/Per-Nilsson/ Optimizely World Shutting down live supportStarting from today the live support feature on Episerver World will be closed. We have seen a decreasing interest for the feature so it makes sense to close it down and instead focus our work on registered support tickets. This is also a step forward to combine the different support organizations within Episerver as the other ones don't use any chat functionality. Please drop me a message if you have any additional questions. 2016-04-13T14:25:43.6000000Z

Blog post

Developer Support will be changing ticket system As a first step to merge and integrate EPiServer's and Ektron's support organizations with each other the former EPiServer Developer Support will change the ticket system from Omnitracker to Zendesk. The change is planned for next week. The former Ektron Support organization is already using Zendesk and the name of the Zendesk instance has already been changed to episerver.zendesk.com. I believe the change will be for the better for you as partner developers due to the more user friendly interface in Zendesk. During the coming weeks/months we will keep both systems running in parallel to make sure the earlier registered cases in Omnitracker can be handled as normal. The email address used for communication for tickets registered in Zendesk will be developersupport@episerver.com but a new will be used for old tickets earlier registered in Omnitracker (developersupport_old@episerver.com). If possible, please make sure that the email address is developersupport_old@episerver.com when you respond to a ticket named similar to DI-123456 once the change has taken place. In case you miss this we will still handle it but will create some extra work. To register a ticket just visit the support pages at world.episerver.com/support as usual.2015-04-10T15:38:30.0000000Z

Blog post

Paypal provider for Commerce R2SP2The API for PayPal has changed since the release of the provider so you will get an exception when trying to connect to paypal. This is the error found in the log: [ERROR] [com.paypal.sdk.exceptions.TransactionException] - The request was aborted: Could not create SSL/TLS secure channel. com.paypal.sdk.exceptions.TransactionException: The request was aborted: Could not create SSL/TLS secure channel. ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation We havent gotten too many requests around the issue to the support but get one every now and then so wanted to share a few lines how to fix it in case you run into it during your project. The only thing needed is to override the default paypal settings like this. Add the following to the <configSections> in web.config. <section name="paypal" type="com.paypal.sdk.core.ConfigSectionHandler, paypal_base"/> Then add the following <paypal> section and you are good to go. <paypal> <endpoints> <wsdl> <environment name="live"> <port name="PayPalAPI">https://api.paypal.com/2.0/</port> <port name="PayPalAPIAA">https://api-aa.paypal.com/2.0/</port> <port name="PayPalAPI" threetoken="true">https://api-3t.paypal.com/2.0/</port> <port name="PayPalAPIAA" threetoken="true">https://api-aa-3t.paypal.com/2.0/</port> </environment> <environment name="sandbox"> <port name="PayPalAPI">https://api.sandbox.paypal.com/2.0/</port> <port name="PayPalAPIAA">https://api-aa.sandbox.paypal.com/2.0/</port> <port name="PayPalAPI" threetoken="true">https://api-3t.sandbox.paypal.com/2.0/</port> <port name="PayPalAPIAA" threetoken="true">https://api-3t.sandbox.paypal.com/2.0/</port> </environment> <environment name="beta-sandbox"> <port name="PayPalAPI">https://api.beta-sandbox.paypal.com/2.0/</port> <port name="PayPalAPIAA">https://api-aa.beta-sandbox.paypal.com/2.0/</port> <port name="PayPalAPI" threetoken="true">https://api-3t.beta-sandbox.paypal.com/2.0/</port> <port name="PayPalAPIAA" threetoken="true">https://api-3t.beta-sandbox.paypal.com/2.0/</port> </environment> </wsdl> </endpoints> </paypal>2013-07-19T16:28:54.0000000Z

Blog post

CMS 7.1 upgrade issuesSince the release of 7.1 we have had a few cases reporting problems with the update and one example is that edit/admin mode ends up being white without any errors. One possible solution for this is to empty the Temporary ASP.NET files for the site and its listed in the Known issues section for the installations <a href="http://world.episerver.com/Documentation/Items/Installation-Instructions/EPiServer-CMS/Version-7/Installation-Instructions---EPiServer-7-CMS/Installation-Instructions---EPiServer-7-1-CMS/">http://world.episerver.com/Documentation/Items/Installation-Instructions/EPiServer-CMS/Version-7/Installation-Instructions---EPiServer-7-CMS/Installation-Instructions---EPiServer-7-1-CMS/</a> We have received cases where this wasn't a solution and are investigating the causes for the issues. It has however been hard to reproduce but it got top priority within EPiServer and we will update the Known issues whenever we have more information. If the section doesn't help for your installation then please report your problem on the link below and if you got an environment where the issue can be reproduced it’s even better:   <a href="http://world.episerver.com/en/Support/Register-Support-Incident/">Register Support Incident</a>2013-04-22T16:41:55.0000000Z

Blog post

MS Update MS11-100 breaks sites with more than 1000 parametersGot a ticket to the support with an error I haven't seen before and found out that the reason is a two weeks old Microsoft hotfix. It might happen to someone else so wanted to write a few rows how to solve it if you run into the problem. During the holidays MS published the security update MS11-100. This update has been released to fix ASP.NET DoS vulnerability and limits the amount of parameters for a single HTTP POST to 1000. It's probably not that often you use more than 1000 parameters but this is the error you will end up with if you do (the one to look for is ThrowIfMaxHttpCollectionKeysExceeded):   Operation is not valid due to the current state of the object. 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. 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: [InvalidOperationException: Operation is not valid due to the current state of the object.] System.Web.HttpValueCollection.ThrowIfMaxHttpCollectionKeysExceeded() +2692302 System.Web.HttpValueCollection.FillFromEncodedBytes(Byte[] bytes, Encoding encoding) +61 System.Web.HttpRequest.FillInFormCollection() +148 [HttpException (0x80004005): The URL-encoded form data is not valid.] System.Web.HttpRequest.FillInFormCollection() +206 System.Web.HttpRequest.get_Form() +68 System.Web.HttpRequest.get_HasForm() +8735447 System.Web.UI.Page.GetCollectionBasedOnMethod(Boolean dontReturnNull) +97 System.Web.UI.Page.DeterminePostBackMode() +63 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +133   Solution: When they added the limitation of parameters they also added the possiblilty to override the default value by a new setting in web.config. Can also mention that it’s not possible to apply different values at different locations.  Add the following setting to web.config with a value larger than 1000 (default): <appSettings>    <add key="aspnet:MaxHttpCollectionKeys" value="some number here"/> </appSettings> The above setting should fix the problem.   Links: Info about the hotfix and people getting the error in the discussion following the article: <a href="http://weblogs.asp.net/scottgu/archive/2011/12/28/asp-net-security-update-shipping-thursday-dec-29th.aspx">http://weblogs.asp.net/scottgu/archive/2011/12/28/asp-net-security-update-shipping-thursday-dec-29th.aspx</a> The same error discussed in a forum <a href="http://forums.asp.net/t/1754522.aspx/1?New+Net+2+0+Bug+From+Windows+Update+">http://forums.asp.net/t/1754522.aspx/1?New+Net+2+0+Bug+From+Windows+Update+</a>2012-01-18T23:40:23.0000000Z

Blog post