The Episerver Perform feed status admin add-in has been updated to be compatible with v2.x of the EPiServer.Personalization.Commerce package that it depends on. The Episerver Perform Feed Status admin add-in allows admin users to see outstanding feed requests and also download the feed file before its picked up by Episerver Perform:
A new version of the cookie visitor group criteria is now available on the Episerver Nuget feed that is compatible with Episerver 11.
The package adds two new visitor groups called "Cookie exists" and "Cookie Value Equals". These visitor groups allow your site editors to personalise content based on whether a cookie exists or on the value contained within a cookie.
A new version of MenuPin is now available. This is is a compatibility release for EPiServer 9 upwards. If you have not heard of MenuPin before then it allows users to pin the menu at the top of the EPiServer UI (as shown in the image).
What's new in v3.0:
- Compatible with EPiServer 9+
When purchasing Episerver Digital Experience Cloud Service customers get access to a SendGrid account to send mail. This configuration is not automatically applied by the standard config transforms applied by Episerver so you need to configure them manually.
This post is a "note to self" to remember the SMTP settings for Episerver Digital Experience Cloud Service in web.config:
It has been a successful year for Episerver with ongoing platform developments, acquisitions, open source modules being released and developer meet ups taking place across the world. These all contributed to an exciting 2016 and an even more exciting 2017 ahead. This post is a quick write up to try and summarise some of the highlights from 2016 in Episerver.
Episerver Perform provides product recommendations on your site. In order to do this it is necessary to send a product catalog feed so the recommendations engine knows which products to recommend. Fortunately there is a pre-built job for this called "Export Product Feed" which comes as part of the EPiServer.Personalization.Commerce package. It creates the catalogue feed file and sends a request to Episerver Perform to come and pick it up as described here https://world.episerver.com/documentation/developer-guides/commerce/personalization/recommendations/. This can also be seen on the image on the below (from the Episerver documentation):
For a while I've wanted to explore the Episerver Nuget Feed in a little more detail than was available on the standard http://nuget.episerver.com page. For example I would like to filter by community submitted versus Episerver packages and also know when packages have been updated and/or submitted, in particular recently updated or added packages. So I decided to put a an Episerver Nuget Feed Explorer tool together that allows users to look at the data available on the Episerver Nuget feed, filter it and facet it:
Episerver Campaign allows users to communicate at scale with outbound messaging on channels such as email, SMS and push notifications. One common requirement is to sign up for a newsletter which is managed and distributed by Episerver Campaign and to ensure that the profile of a user is the available when clicking a link in a email that opens on another device such as a smart phone or even another browser.
This post describes how its possible to load recipient information for user from Episerver Campaign using the Episerver Campaign Connector based on an inbound link to a site. The following steps describe what needs to happen:
A new version of MenuPin is now available. This is is a compatibility release for EPiServer 8 upwards. If you have not heard of MenuPin before then it allows users to pin the menu at the top of the EPiServer UI (as shown in the image).
What's new in v2.0:
- Compatible with EPiServer 8+
- Its now available as a standard Nuget package on the EPiServer Nuget feed (its no longer an Add-on)