New Alloy templates package for EPiServer 7 is a good example of building adaptive site and using new EPiServer features like shared blocks. It implements custom content area rendering to arrange blocks in rows and fill all available space depending on current browser size. There is couple of known issues related to these rendering tricks.
This blog post provides brief technical information about Add-On Store in EPiServer 7 Preview and describes the process of developing simple add-on step by step. Meet the Add-On Store Add-on Store is the new approach to create, distribute, share and manage modules for EPiServer based sites.For site owners and administrators Add-On Store is the one
New Orchard 1.4 brings new Autoroute feature, built-in Projector module, must have set of field types (finally) and the number of bug fixes. It comes with breaking change by removing Route part, which means that you have to use special module to migrate your existing site content to version 1.4. Content migration and Title module
This blog post describes EPiServer CMO installation and configuration in a load balanced environment where CMS editing interfaces and components are not available on the front-end web servers; additional editing server is set up and attached to the same database. This kind of environment is described in this blog post as Option 2. So let’s
Load balancing is a clear choice for the most of popular sites with high volumes of incoming traffic. This solution allows distributing the load among several servers to improve performance and achieve high availability. This blog post describes а simple case of EPiServer CMO installation and configuration in the hosting environment where load balancing is
This blog post describes several options for advanced EPiServer CMO deployment. You may have more than one server, for example when site database is hosted on the separate back-end machine. You can consider the following options to distribute the work across servers: CMO database on the separate server. It sounds logical to keep CMO database
Running EPiServerCMO.msi you get CMO installed to EPiServer CMS module folder, by default it is C:\Program Files (x86)\EPiServer\CMS\6.1.379.0\Install\Modules\CMO184.108.40.206. Now it can be installed on specific web site using Deployment Center. Installation instructions for EPiServer CMO 2 R2 pretty well describe simple deployment model with the one front server. By default all CMO components are deployed
Problem Using EPiServer WebDAV you can face with following issue: after setting up WebDAV in EPiServer CMS and client configuration you still cannot access your web folder. Depending on client software you can get different error messages. Windows explorer says that it cannot access your resource and suggests to check name spelling. Other clients return