Take the community feedback survey now.
Take the community feedback survey now.
Follow bloggers on Optimizely World to get the latest from people who know all about the Optimizely platform! You will find blog posts from the entire Optimizely community, as well as from the Optimizely development teams.
Start blogging - create your own blog (requires log in)
Manage your blog posts on Optimizely World (requires log in)
Rules for blogging on Optimizely World
A week ago we upgraded EPiServer World to the release candidate for EPiServer CMS 6 with the motto “Drinking our own champagne” and put it to the real test. I have previously written about upgrade experiences for EPiServer CMS 5 R2 and its breakin...
Objective Collect and transform data collected by XForms using SSIS. Recently i ran into a situation where i needed to collect data from EPiServer (XForms) using SSIS. At first, i had a few possible ways to solve this task. Use SQL and collect t...
A quite common request I have heard a number of times is the need to take a snapshot of a web site and store it securely, in order to in the future be able to proof what was stated on the site at a given date. I know a number of EPiServer customer...
There is plenty of talk about MVC vs. Web Forms going on. One thing that MVC pushes for is small controller classes and a rich domain model. A rich domain model is equally useful in Web Forms but somehow seldom implemented. Using a tiered design,...
This post will give you some background in how caching works in Dynamic Data Store (DDS) and give you knowledge of what to expect when it comes to object instances and such when working with DDS. Problem with caching The classical problem when it...
Configuration vs Code – it’s a classic dilemma. Both have their ups and downs. However, I am the kind of guy that tends to prefer code over configuration (you already guessed, I’m sure). Today I got a question if it’s possible to attach a page...
I am sad to announce that we had to do a behavioral change in the gadget Ajax framework. Previously when you did an Ajax call (using the gadget framework, gadgetInstance.ajax({..}) ) we loaded the default view of the gadget ( gadget.loadView() )...
I am sad to announce that we had to do a behavioral change in the gadget Ajax framework. Previously when you did an Ajax call (using the gadget framework, gadgetInstance.ajax({..}) ) we loaded the default view of the gadget ( gadget.loadView() )...