Working with multi lingual formatting is fairly simple in Episerver CMS. It’s simply a matter of relying on a set of key implementations, such as ContentLanguage.PreferredCulture or CultureInfo.CurrentUICulture, when explicitly formatting an object or struct to it’s localized representation. One detail, which I’ve seen being left out by developers, is the fact that code executed in the context of an
I am very happy to announce the first Episerver Meetup, at Valtech, in New York City. It will be hosted at Valtech’s amazing New York office, which is located in the vibrant Meatpacking District – more precisely at 416 W 13th St, Suite 309, New York, NY 10014. Episerver and Valtech will be presenting some new and exciting things, and
Episerver’s multi-site feature is a really powerful feature when dealing with enterprise solutions. It supports the need to create more than one site running on a single instance (code base). I have, quite recently, used this feature to create dedicated brand experiences and a loyalty program site for a unified Commerce experience. We are often facing the same issue when
Translations.com has provided a Translation Connector to the Episerver community that ties Episerver Commmerce and Episerver CMS – being Pages, Blocks and Catalog items – with their existing GlobalLink Translation suite. Large Episerver solutions tend to require custom Content Types, which also requires translation during the authoring flows, via customized ContentProviders. My experience tells me that business users expects that
Episerver Find is considered a near-realtime search engine. It’s achieved via a event-driven strategy that automatically propagates content-changes to the Search Index whenever Content changes in either Episerver CMS or Episerver Commerce. We’ve experienced that Episerver Find can have a hard time managing large – as in thousands – sets of bulk changes. What we meet is an exception indicating
Our solutions are expected to work in a stateless environment where session affinity (sticky sessions) is disabled. ASP.NET MVC, which is the .NET web foundation of most Episerver projects, are considered stateless with a few exceptions. One of them is their persistence of temporary data across requests. Getting management of temporary data in a distributed setup is fairly simple. There are
Recently we had to support custom segments as part of the Hierachical routing mechanism put in place for Commerce. Optimization of the User Experience required us to support a section specific URL on a fairly advanced product presentation page. Essentially, we needed to support that specific sections – e.g. Model Specifications or Accessories – could be shared and directly targeted – i.e. that http://www.commerce.com/cars/vans/model-x/accessories/ were directly