This content is archived. See latest version here.

Last updated: Mar 31 2014

This document provides an introduction to asset management in EPiServer, and media type of content in particular. The EPiServer platform has an asset management system supporting used by EPiServer products such as CMS and Commerce. Assets are made available in the user interface in the assets pane, for instance blocks and media files in CMS, and the product catalog in Commerce. Media types can be for instance images, videos and documents. Media types, just as any other content type, have to be defined before it is possible to for example upload an image.

Refer to Media types and templates for defining types for media. Refer to BLOB storage and BLOB providers to change storage model for media, such as BLOB provider.

How it works

The assets system is based on a typed model with support for the following property types:

  • ContentReference property type with a UIHint “image” will be displayed and edited as an image.
  • ContentReference property type with a UIHint “video” will be displayed and edited as a video.
  • ContentReference property type with a UIHint “mediafile” will be displayed and edited as any file.
  • Url property type with a UIHint “image” will be displayed and edited as an image.
  • Url property type with a UIHint “video” will be displayed and edited as a video.
  • Url property type with a UIHint “document” will be displayed and edited as any file.

The following functionality is available for all content types:

  • Waste basket support for all content types, including moving, viewing and restoring from trash.
  • Checking of references when deleting any content item (image, page, block etc) reference dialog with links to affected content references.
  • Drag and drop support from the media manager in the assets pane to any overlay or editor that handles files (ContentReferences or URLs with a “mediafile”, “image”, or “video” UIHint).

Changing maximum file size for upload

In web.config, change the parameters maxAllowedContentLength and maxRequestLength:

XML
<system.webServer>
  <security>
    <requestFiltering>
      <requestLimits maxAllowedContentLength="1048576000" />
    </requestFiltering>
  </security>
</system.webServer>

See also

Comments