Showing posts from June, 2014

Error handling in IIs 7

Not a new topic but I come across a situation when our offshore team was not able to see the error details. This is reminder if someone forgets that.

In IIS 7.0 The <httpErrors> element allows you to configure custom error messages for your Web site or application. <CustomErrors> won't work.

Click for further details on httperrors

httpError Elements

EPiServer Error handling

Example Production Enviornment Settings
<httpErrors errorMode="Custom" existingResponse="Replace">
      <error statusCode="404" path="/Page404.html" responseMode="ExecuteURL"/>
      <error statusCode="500" path="/500-error-page.html" responseMode="ExecuteURL"/>

Developers Environment Settings:
With Settings
<httpErrors errorMode="Custom" existingResponse="Replace"></httpErrors>
Error Details on screen will be like this

With Settings
<httpErrors erro…

Blocks for EPiServer Commerce Catalog Nodes

Can we use Blocks with Catalog nodes? In theory Yes, what can stop you. We had a requirement when CMS editor can add a Carousel Block to Catalog Nodes. But Block Gadget was not available in CMS Catalog Edit Mode. Only available gadgets were Catalog, Media, Latest and Versions. From architecture point of view I was convinced that we can add ContentArea for Catalog Nodes and Blocks can be reused for Catalog Nodes also. I googled the issue and find an answer by Linus. Its simple I want to keep solution as a self note.

Add the following section under your <> section in web.config and the blocks gadget should appear for the commerce view (given that you have not customized your view):<viewManager> <views> <add name="/episerver/commerce/catalog"> <settings> <add name="AddSharedBlocks" transformationType="Add" definitionName="EPiServer.Cms.Shell.UI.Components.SharedBlocksComponent" plugInArea="/epise…