Custom web development NJ solutions from the leading NJ web development company offering custom websites, online databases and web hosting.

System Requirements

1. Community Server 2008
2. Audio/Video codecs installed on server
3. EdgeConvert installation package

Release Notes

1. Currently, this only works with file system based storage, does not work with Amazon S3.

Installation Instructions

You should have received the installation package separately via email. Here are the steps to install the EdgeConvert package into Community Server 2008. The updates to the AggregatePostList.ascx file were made to the base version included with the Hawaii theme. You can make similar updates to the corresponding page on any of the other themes.

Step 1: Copy Files

1. Copy the edgeconvert folder to the root (Web) directory of your CS website. You must give this folder Read/Write permissions for the account your website uses, such as Network Service.
2. Copy the contents of the bin folder to the bin folder of your CS website.
3. If you do not have a CommunityServer_override.config file, copy CommunityServer_override.config into the root of your CS installation. Otherwise, copy the override in the supplied CommunityServer_override.config file and paste it into your existing file.

Step 2: Update AggregatePostList.ascx

1. Locate your theme's AggregatePostList.ascx control. For example, in the Hawaii theme, this is located in /Web/Themes/Hawaii/Media/AggregatePostList.ascx
2. If you have not modified your theme’s AggregatePostList.ascx control, replace the AggregatePostList.ascx control with the one provided with this distribution
3. If you have modified your theme's AggregatePostList.ascx control, perform the following:
   1. Copy the <%@ Import Namespace … %> tags into the top of your existing control
   2. Copy the <script> tag contents
   3. Replace the entire <CSMedia:MediaGalleryPostList> with the one supplied in this distribution.

Step 3: Update AjaxMediaSlideshow.ascx

1. Locate the file AjaxMediaSlideshow.ascx, located in your \Utility\UserControls directory
2. If you have not modified your AjaxMediaSlideshow.ascx control, replace the AjaxMediaSlideshow.ascx control with the one provided with this distribution
3. If you have modified your AjaxMediaSlideshow.ascx control, perform the following:
   1. Copy the <%@ Import Namespace … %> tags into the top of your existing control
   2. Copy the <script> tag contents
   3. Replace the entire <CSMedia:MediaGalleryPostList> with the one supplied in this distribution.

Step 4: Copy Video Codecs to your server

If any of these are installed already, you do not need to re-install them.

1. To convert Windows Media (AVI, WMV, ASF, WMA, WAV, using any AVI/WM codecs like DIVX, XDIV, etc), install the latest version of Microsoft Windows Media Player:
   http://www.microsoft.com/windows/windowsmedia/
   Note: For Windows 2003, please read the following KB article:
   http://www.blue-pacific.com/support/kb/article.aspx?id=10926&cNode=3Q1G2S
2. To convert QuickTime Media (MOV, QT, DV, AAC, AIF/AIFF, etc), install the latest version of Apple QuickTime Player, found here: http://www.apple.com/quicktime/download
3. If converting Real Media (RM, etc) then install Real Alternative:
   http://www.codecguide.com/download_real.htm
4. Download and install the codec pack from here – accept all default options: http://www.cccp-project.net
5. Download these registry settings for ffdshow and import into your registry: ffdshow_settings.zip
6. Reboot the server

Step 5: Test it out!

You should now be able to upload video files to Community Server, and they will be converted to FLV format and play using the built in FLV player. You should also see thumbnail images (taken from frame 1 of your video) on the thumbnail pages.

If you have any problems, please don't hesitate to email us at support@busedge.com.

Troubleshooting

Here are some troubleshooting steps in case you are having problems:

1. Timeouts: There are a 2 places that a timeout can occur. The first is when uploading the file. If the video file is large and the person uploading has a slow connection, the upload can timeout. The 2nd place is when EdgeConvert is performing the actual conversion. Here are all the places to add timeout values to ensure uploads work properly:

1. Web.Config: Add a httpRuntime section under System.Web as follows
   

   <system.web>
     <httpRuntime executionTimeout="1200" maxRequestLength="32768" />
   </system.web>
   						

   This will increase the allowable file size to 32 MB and set the execution timeout to 1200 seconds. You should alter these values as necessary.
   
   
2. Add Server.ScriptTimeout values to the CreateEditePost and the UploadPostAttachment pages. Add the following code to the top of the page just after the @Page directive:
   /themes/themename/media/createeditpost.aspx
   /themes/themename/media/uploadpostattachment.aspx
   /themes/hubs/themename/media-createeditpost.aspx
   /themes/hubs/themename/media-uploadpostattachment.aspx
   

   <script runat="server">
   	void Page_Load() {
   		HttpContext.Current.Server.ScriptTimeout=1200; 
   	}
   </script>
   					

   This is in seconds. You can alter this value based on your testing.

2. Video doesn't play in the player: This could be due to a missing mime type in IIS. Go to IIS, then right click on your website > Properties. Under HTTP Headers, click MIME Types. Click New. Enter ".flv" for the extension, and "video/x-flv" for the MIME Type (without the quotes). Check to see if your videos play now.

3. Some large videos still fail to upload, and Community Server event log shows a lot of "directory change notification" errors. This is due to IIS monitoring your website directory structure for directory changes and consequently resetting the application process. Here is the article explaining the problem and how to fix it: http://support.microsoft.com/kb/911272. You should change FCNMode to 1. There is a problem with this however, this means that IIS will no longer detect any changes that you make to files in the website, such as web.config changes or any aspx page changes. After each change, you will need to recycle the app pool in order to see the changes reflected in your site.