• Blocks not showing on site after publishing page

    Description A common issue is to see new blocks not showing up after publishing the page they live on.  Steps Blocks must be published before they will show up on a page. The latest version of Episerver.Labs.BlockEnhancements(which is a separate package) addresses this with a feature called smart publish which identifies blocks associated with the page and asks the user if the blocks should be published. This is not available by default and requires the addition of the Episerver.Labs.Bl...

  • Options window blank after upgrading

    Description After upgrading one may see that the options window is not showing any options. This is the same issue described in this post. Content data null Resolution EPiServer.Marketing.Testing 2.5.5 has been released which fixes this issue: https://nuget.episerver.com/package/?id=EPiServer.Marketing.Testing&v=2.5.5 After upgrading, be sure to completely clear the browser resources. This includes clearing local storage, session storage and site cookies. In Chrome, the "Cook...

  • Clarifications on archiving and expiring content in Episerver

    Description We have had a couple tickets regarding confusion on expiring content and the archive functionality and what is the expected behaviour. Resolution When working in Episerver content can be set to expire by clicking Tools > Manage Expiration and Archiving in the content properties. On expiration the content will no longer be visible to users from the front end of the site. The content can either be set to expire immediately or for a later point in time. The archive fu...

  • Unable to view draft versions of blocks on pages

    Description If edits are done to blocks you may find that those edits do not show when viewing the pages the blocks are hosted on. Even in preview mode you may not see those block changes until they are published.  Resolution "Content Areas can show the draft version of the block, if the page and block are in the same project and that project is active." To allow viewing of the draft versions of blocks, ensure the relevant pages and blocks are in the same active project. Forum...

  • Media assets give 404 errors while CMS UI shows images

    Description In some cases you may see images give 404 errors on the front end of an Episerver site even though the images have clearly been uploaded and show in the CMS UI.  Resolution Typically this is due to the image not being published. Just like pages and blocks, assets need to be published to see the changes on the front end. 

  • Failed loading content in Episerver project

    Description This article describes an error that can occur when switching projects using the Episerver Project feature. It will appear in a modal dialog with the following for example.Failed loading content with the url/uri: epi.cms.contentdata:///10260 Further review into the log and browser console will show these messages. In the log these items will appear:"Error: Unable to load /EPiServer/shell/Stores/context/?uri=epi.cms.contentdata%3A%2F%2F%2F4745_22775&epiprojects=4&epieditmode=...

  • Unrelated documents visible under asset pane "For this block"

    Description This article describes an issue when a new block is created there are unrelated documents that appear under the asset pane in the "For this block" section. A similar issue was found in an upgraded site from 7.1 to latest Episerver. Product Development investigated and found that somehow there was some content under the contentRootFolder that did not belong. It could have happened during migration of vpp files or Blobs. Resolution The solution was to move those conte...