Episerver’s (now Optimizely) continuous release cycle provides new features and bug fixes on a bi-weekly cadence. Every other month, C2 will aggregate and highlight some of the bigger updates to Optimizely software. To learn more, or if you have specific questions, you can contact The C2 Group, an Optimizely Gold Partner, here.
Fixed in: EPiServer.Commerce 13.26.0 [ID: COM-11747]
Episerver has added the ability to add placeholders of custom code within the Order Management module. This allows partner developers to add new features to the Order Management module that can address the specific needs of a client.
Fixed in: EPiServer.Commerce 13.25.0 [ID: CPM-11929]
Each item on an order now contains a direct link to the product page on the website. This makes it easier for the customer service representative to troubleshoot an issue and verify the product in question. To learn more about the Order Management screen, click here. To learn how to extend the search result display, click here.
Fixed in: EPiServer.Commerce 13.25.0 [ID: COM-11703]
Recent updates to the promotion engine have reduced the load from the database and increased the speed of processing requests for discounts during page load. Along with adding a cache into the mix, these optimizations allow for a faster loading product detail page and a better customer experience.
Fixed in: EPiServer.Profiles.Client 1.22.0 [ID: PROF-7090]
Visitor Intelligence tracks both known and anonymous users through various channels. Users are given a profile and can be tracked by profile events via a number of different channels. This most recent update improves the ability to delete profiles and all related events. Once complete, these deleted profile events are not available through the API or UI. These same devices can be tracked in the future although a new profile will be created for them.
Fixed in: EPiServer.Profiles.Client 1.22.0 [ID: PROF-7089]
Additional improvements were made for deleting profile events by a tracking ID. Now, a profile event or series of events that share a tracking ID can be deleted. Once complete, the events will not be available through the API or UI. Future events can still be tracked by this same tracking ID and utilized within segments.
Fixed in: EPiServer.CMS.Core 11.20.0 [ID: CMS-16332]
Before this fix, the XhtmlString (think Rich Text Editor) and the content area properties utilized more memory than was needed for the content being stored. This overuse of memory caused sites with a larger amount of content to use a lot more memory than was necessary. This update will increase the efficiency of memory usage especially on sites that utilize the Rich Text Editor and Content Areas heavily.
Fixed in: EPiServer.CMS.Core 11.20. [ID: CMS-16119]
The IPermanentLinkMapper is essential in making sure that links on a page still work when a content item’s name changes. With this update, IPermanentLinkMapper now can batch resolve the links on a page and processes them more efficiently. This reduction of overhead from the previous method has increased the processing speed significantly.
Fixed in: EPiServer.ContentDeliveryApi 2.17.0 [ID: HAPI-684]
Episerver has simplified the code and QA process for the content delivery api by removing the v3 APIs. All the features that were a part of the v3 APIs have been backported to v2 rendering the v3 API unnecessary. The only remaining issue between the two was a slight difference in the JSON format which was addressed. Episerver has added an option for the developer to exhibit more control over the JSON.