Embedding a Youtube Video on EPiServer

Embedding youtube video

Several pages in our website require embedded Youtube videos. So I created a Youtube block that accepts the following Content properties:

  • Title
  • Description
  • Embed link

While it’s Settings properties are:

  • Width
  • Height
  • Allow Full Screen
  • Auto Play

Here’s my code for the model:

 public class YoutubeBlock : BlockData  
 {  
      [Display(  
           Name = "Title",  
           GroupName = SystemTabNames.Content,  
           Order = 10)]  
      public virtual string VideoTitle { get; set; }  
      [Display(  
           Name = "Description",  
           GroupName = SystemTabNames.Content,  
           Order = 20)]  
      public virtual string Description { get; set; }  
      [Display(  
           Name = "Url to Youtube Video",  
           GroupName = SystemTabNames.Content,  
           Order = 30)]  
      [Required]  
      public virtual Url YoutubeLink { get; set; }  
      [Display(  
           Name = "Width",  
           GroupName = SystemTabNames.Settings,  
           Order = 10)]  
      public virtual int Width { get; set; }  
      [Display(  
           Name = "Height",  
           GroupName = SystemTabNames.Settings,  
           Order = 20)]  
      public virtual int Height { get; set; }  
      [Display(  
           Name = "Allow Full Screen?",  
           GroupName = SystemTabNames.Settings,  
           Order = 30)]  
      public virtual bool AllowFullScreen { get; set; }  
      [Display(  
           Name = "Auto Play?",  
           GroupName = SystemTabNames.Settings,  
           Order = 40)]  
      public virtual bool AutoPlay { get; set; }  
      public override void SetDefaultValues(ContentType contentType)  
      {  
           this.AllowFullScreen = true;  
           this.AutoPlay = false;  
           this.Width = 520;  
           this.Height = 292;  
      }  
 }  

Nothing special with my controller:

 public class YoutubeBlockController : BlockController<YoutubeBlock>  
 {  
      public override ActionResult Index(YoutubeBlock currentBlock)  
      {  
           return PartialView(currentBlock);  
      }  
 }  

And then my View:

 @model YoutubeBlock  
 <div class="youtubediv">  
   @if (String.IsNullOrEmpty(Model.VideoTitle))  
   {  
     <h3>@Html.PropertyFor(y => y.VideoTitle)</h3>  
   }  
   @if (String.IsNullOrEmpty(Model.Description))  
   {  
     <p>@Html.PropertyFor(y => y.Description)</p>  
   }  
   @{  
     var youtubeLink = Model.YoutubeLink.OriginalString;  
     if (Model.AutoPlay)  
     {  
       youtubeLink += ((youtubeLink.Contains("?")) ? "&" : "?") + "autoplay?=1";  
     }  
     var allowFullScreen = Model.AllowFullScreen ? "allowfullscreen" : "";  
   }  
   <iframe width="@Model.Width" height="@Model.Height" src="@youtubeLink" @allowFullScreen style="border: none;"></iframe>  
 </div>  

The recommended way of embedding video is to use the iframe. However, you can also use the elements Object and Embed as per W3schools.

Meanwhile on the EPiServer CMS Edit mode…

 

 

How to Create an RSS Feed in EPiServer (ASP.NET MVC)

Thanks to Ted and a guy from CodeInside for your blogs which helped come up with this solution.

Problem: Create an RSS feed for ASP.NET MVC Website with EPiServer

Solution: We need three things

1. RssResult class
2. RssPage page type
3. RssPageController which creates the xml rss feed

So let’s begin with the RssResult class. This class needs to inherit FileResult (System.Web.Mvc) passing rss+xml as content type.

 public class RssResult : FileResult  
{
private readonly SyndicationFeed _feed;
public RssResult(SyndicationFeed feed)
: base("application/rss+xml")
{
_feed = feed;
}
public RssResult(string title, List<SyndicationItem> feedItems)
: base("application/rss+xml")
{
_feed = new SyndicationFeed(title, title, HttpContext.Current.Request.Url) { Items = feedItems };
}
protected override void WriteFile(HttpResponseBase response)
{
using (XmlWriter writer = XmlWriter.Create(response.OutputStream))
{
_feed.GetRss20Formatter().WriteTo(writer);
}
}
}

Then, we create a model page type which I’ve named RssPage.cs. It basically only has one property which holds the root page of the RSS

 [ContentType(  
DisplayName = "Rss Page",
GUID = "2ba86356-847f-439f-bf1c-36f7cf70158e",
Description = "Used to create an RSS Feed")]
public class RssPage : SitePageData
{
[Display(
Name = "RSS Root Page",
GroupName = SystemTabNames.Content,
Order = 10)]
[Required]
public virtual PageReference RssPageLink { get; set; }
public PageDataCollection GetPages()
{
var pages = DataFactory.Instance.GetChildren(RssPageLink);
return FilterForVisitor.Filter(pages);
}
}

Now we create the controller for this page type.

 public class RssPageController : PageControllerBase<RssPage>  
{
public ActionResult Index(RssPage currentPage)
{
return Feed(currentPage);
}
public virtual ActionResult Feed(RssPage currentPage)
{
var items = new List<SyndicationItem>();
var newsPages = DataFactory.Instance.GetChildren<NewsPage>(currentPage.RssPageLink);
var pageUri = currentPage.RssPageLink.GetUri();
foreach(var newsPage in newsPages)
{
var feedPackageItem = new SyndicationItem(newsPage.PageTitle, newsPage.Description, pageUri);
feedPackageItem.PublishDate = newsPage.StartPublish;
items.Add(feedPackageItem);
}
return new RssResult("My News Feed", items);
}
}

Now we create an instance of this page on EPiServer.

Navigating to this page now shows an xml rss page

Any questions, please comment!

EPiServer 7.x vs EPiServer 8

I was tasked to find out whether our current active license for CMS 7 will still work with EPiServer 8. So I did some research and thought of sharing it here as well.

Summary Version:

  • Good news – Our 7.x license will continue to work for EPiServer 8.0
  • Current EPiServer version available in NuGet is 8.3.0.
  • EPiServer 8 has breaking changes but mostly needing just code recompilation
Long Version:
Here’s the forum that confirms our active subscription will continue to work for this new major version.

If the customer has an active subscription the license that has been used for 7.x will continue to work. When it comes to how certifications are handled for new major versions we will soon give you an update on that. But, rest assured, your EPiServer 7 certification will continue to be valid.

EPiServer has started a continuous release process since about a year ago. Checking their last releases, here’s what is recent…

Updating to CMS 8 is no different from updating to the feature updates delivered via NuGet. They have however, named it to a major version and this is because it has some breaking changes. List of breaking changes here: http://world.episerver.com/documentation/Items/Upgrading/EPiServer-CMS/8/Breaking-changes/
Some of the new features:

  • Multi-publish and preview – there’s a new concept called ‘Projects’ in the Editor
  • Performance Improvements
  • Updated browser support – IE9 is no longer supported!
  • Support for canonical URLs
  • Better ways to organize content types and properties
  • Improved control to ensure design consistency
Other links I thought are useful:

Hope this helps anyone!

Int64 / Long / Bigint Property is not supported in EPiServer 8

Yes, you read it right. You can’t have a model property of type Int64 / long.

I came across an issue where in I have a model that requires to store an Id (from the database) as one of it’s properties. It so happens that most tables we have at work go by an Id of type Bigint (SQL Server).

So I had to create something like:

 public class MyModel {  
[Editable(false)]
[BackingType(typeof(PropertyNumber))]
public virtual long SomeObjectId { get; set;}
// and some other properties below...
}

However, when I run the app, I get the following error:

Type ‘System.Int64’ could not be mapped to a PropertyDefinitionType

Yes, PropertyNumber only supports Int32, etc.

So I fixed this by changing the data type to string so it stores the Int64 as string, but parse it back when I need it as Int64.

 public class MyModel {  
[Editable(false)]
[BackingType(typeof(
PropertyString))]
public virtual string SomeObjectId { get; set;}
// and some other properties below...
}

Notice that I also updated the backing type.

I’m not sure if this is the best way of playing with Int64’s, but it solved my problem!

PS. Looks like this has been the case ever since

Using XForms in EPiServer 8 MVC

Ha, another milestone for me – I was able to create an XForm in EPiServer and hook it up to a block!

First step I took:  Create a Form block, which consists of the following properties:

 public class FormBlock  
{
public virtual string Heading { get; set; }
public virtual XForm Form { get; set; }
[Ignore]
public virtual string ActionUri { get; set; }
}

And then create a controller that populates the ActionUri property. Here is what it looks like:

 public class FormBlockController : BlockController<FormBlock>  
{
private readonly PageRouteHelper pageRouteHelper;
public FormBlockController(PageRouteHelper pageRouteHelper)
{
this.pageRouteHelper = pageRouteHelper;
}
public override ActionResult Index(FormBlock currentBlock)
{
// Create postback url
if (currentBlock.Form != null && this.pageRouteHelper.Page != null)
{
var actionUri = "XFormPost/";
actionUri = UriSupport.AddQueryString(actionUri, "failedAction", "Failed");
actionUri = UriSupport.AddQueryString(actionUri, "successAction", "Success");
currentBlock.ActionUri = actionUri;
}
return PartialView(currentBlock);
}
}

The view is short and simple:

 @model FormBlock  
<h2 @Html.EditAttributes(m => m.Heading)>@Model.Heading</h2>
@using (Html.BeginXForm(Model.Form, new { Action = Model.ActionUri}))
{
Html.RenderXForm(Model.Form);
}

2nd step: Create a Page Type where one of it’s properties is the newly created Form block

 public class FormPage  
{
public virtual FormBlock FormBlock { get; set; }
}

And then create the Controller. Since the ActionUri in the Form block has been set to “XFormPost/”, we create that Action method as you can see below. I have also added Success and Failed actions that need to be further implemented. But for now, we leave it as is.

 public class FormPageController : PageControllerBase<FormPage>  
{
private readonly XFormPageUnknownActionHandler _xformHandler;
private string _contentId;
public FormPageController()
{
_xformHandler = new XFormPageUnknownActionHandler();
_contentId = string.Empty;
}
public ActionResult Index(FormPage currentPage)
{
var model = new PageViewModel<FormPage>(currentPage);
return View(model);
}
[AcceptVerbs(HttpVerbs.Post)]
public virtual ActionResult XFormPost(XFormPostedData xFormpostedData, string contentId)
{
_contentId = contentId;
return _xformHandler.HandleAction(this);
}
#region Success and failed actions
[AcceptVerbs(HttpVerbs.Post)]
public ActionResult Success(FormPage currentPage, XFormPostedData xFormPostedData)
{
var model = new PageViewModel<FormPage>(currentPage);
return View("Success", currentPage);
}
[AcceptVerbs(HttpVerbs.Post)]
public ActionResult Failed(FormPage currentPage, XFormPostedData xFormPostedData)
{
var model = new PageViewModel<FormPage>(currentPage);
return View("Failed", currentPage);
}
#endregion
}

And finally the View:

 @model PageViewModel<FormPage>  
@{
Layout = "~/Views/Shared/Layouts/_SomeLayout.cshtml";
}
<div class="row">
@Html.PropertyFor(p => p.CurrentPage.FormBlock)
</div>
<div class="row">
@Html.PropertyFor(p => p.CurrentPage.NonTextContent)
</div>

3rd step: Run and create an instance of the Form Page. On the Form block, you can choose which XForm to use in the block.

Or you can also create a new one if needed.

EPiServer: Create a Gallery / ImageSlider Block

One of the tasks I needed to do was to create a block that takes in a list of Images and displays these in an ImageSlider, with the help of almighty Javascript. This might not be the best solution for it, but hey it works.

First of all, I created a Block Type and gave it one property

 public class ImageSliderBlock : BlockData  
{
public virtual LinkItemCollection Images { get; set; }
}

I then created a simple controller to return a View:

 public class ImageSliderBlockController : BlockController<ImageSliderBlock>  
{
public override ActionResult Index(ImageSliderBlock currentBlock)
{
return PartialView(currentBlock);
}
}

And then created a strongly typed View. I gave it an Id

 @model ImageSliderBlock  
<div id="home_slideshow">
<ul class="slideshow show-buttons">
@foreach (var image in Model.Images)
{
<li>
<a href="@image.Href">
<img src="@image.GetMappedHref()"/>
</a>
</li>
}
</ul>
</div>

The Styles and JS will do the trick of displaying these images in the form of a slideshow.
For those who need these files, hit me up!

Meanwhile, in the EPiServer Edit View of the block, you can now drop images in the block!

EPiServer: Attach Database Failed – Access is Denied

I wanted to explore the EPiServer 8.0 database and so I went to clone the MDF file located within my solution and placed the copy in a backup folder. I then went to open SQL Management studio and tried attaching the MDF file:

1. Right Click on the Databases folder
2. Click ‘Attach’
3. Find the ‘Add’ button and click it where a File Browser window will open
4. Locate the file and click OK

However, I got an error along the lines of: “Attach Database failed – Unable to open the physical file – Access is denied”

Two things I did to make it work:

1. Move the .mdf file to the correct SQL path

I moved the mdf file to the following path (I’m using SQL Express):
C:Program FilesMicrosoft SQL ServerMSSQL11.SQLEXPRESSMSSQLDATA
For the full SQL, it should be something like:
C:Program FilesMicrosoft SQL ServerMSSQL11.SS2012MSSQLDATA

And then did the same steps to attach a DB file above. However, I was still getting the same error. So I went to try this next step

2. Run SQL Server Management Studio as Admin. Did the same steps as above and voila. It worked.

I tried doing only step 2 without 1 but it fails. So the solution is basically a combo of both steps.

EPiServer: Auto-create child pages on ‘Add New Page’

I spent almost a day trying to figure this out. I’ve seen heaps of examples on the internet on how to programmatically create pages in EPiServer, but it was a struggle finding a resource that explained where we can do this. Or where we can insert such code. When I finally found a solution, I felt proud. And happy. And this lead me to creating a new blog. Yay for my very first post!

Problem: On add of a new page via the EPiServer Edit page, the system should determine if the page type selected requires children to be created automatically under it.

Solution: We need two things: A new Attribute that can be attached to page types. And a class of the IInitializableModule (EPiServer.Framework) which intercepts creation of pages, checking if the page type has this new Attribute. If it does, it will call a method that will create children under it.

Sounds simple right? But I was new to EPiServer, still am actually. So I thought of creating a blog where I can write about my journeys in EPiServer hoping that someday these struggles I have and the ones I will be going through can be avoided in the future by someone like you who happens to have found my page.

So here’s how my Attribute class looks like

 [AttributeUsage(AttributeTargets.Class, AllowMultiple = true)]  
public class EnsureSubPageAttribute : Attribute
{
public Type PageType { get; set; }
public string PageName { get; set; }
public string UrlSegment { get; set; }
public int SortIndex { get; set; }
public string SetReferenceToProperty { get; set; }
public string[] SetPropertyNames { get; set; }
public string[] SetPropertyValues { get; set; }
}

And then create a Class that goes by the interface IInitializableModule.
Implement members by attaching an event handler when a page is created.

 [InitializableModule]  
public class EnsureSubPages : IInitializableModule
{
#region IInitializableModule Members
public void Initialize(InitializationEngine context)
{
DataFactory.Instance.CreatedPage += Instance_CreatedPage;
}
public void Uninitialize(InitializationEngine context)
{
DataFactory.Instance.CreatedPage -= Instance_CreatedPage;
}
#endregion

Then of course, implement the event handler method.

Once this is implemented, we go ahead and attach the attribute to the appropriate page types.
Here’s an example:

 [EnsureSubPage(  
PageType = typeof(ChildPage),
UrlSegment = "give-it-a-url")]
public class AutoParentPage : SitePageData
{
}

Any questions, just comment! Thanks