Products » Knowledge Base » Url Master 

Url Master Help Wiki

BizModules Ultra Video Gallery


Compatibility

The Ultra Video Gallery module is compatible with the Url Master module, but requires some configuration changes.  These changes depend on the version of the UVG module.

You will need a minimum version of 2.4.3 of the Ultra Video Gallery module, this version contains important fixes for Url Handling. Earlier versions may return errors on some pages.

UVG Versions 2.x

Issues

You may find some features not working correctly, errors related to the 'NeatUpload' module, and/or Ajax features working incorrectly.

Configuration

1) If not already this way, the 'NeatUpload' component must be moved to the top of the list of httpModules in the or sections of the web.config file. Primarily, it needs to be above the UrlRewrite entry, but it is simpler to move it to the top of the list.

2) Case Sensitive Querystring Parameters

If using 1.14.10 or earlier of Url Master, you can't use the 'force lower case' option of the Url Master module, as UVG has some case-sensitive querystring parameters.

If using 1.14.11 or later of Url Master, you can use the 'force lower case' option, but you will need to exclude the pages with UVG on them by creating a regex pattern, and placing it into the 'Do not change case of urls that match this regex' field, under the 'Advanced Regex Settings' section in the Friendly Url Settings page. If you do not know how to construct regex patterns, it is advisable just to not use the 'force lower case' option.

3) Ajax features : you will need to include |/ajaxpro/ into the 'ignoreRegex' pattern. See Modifying Advanced Regex Patterns for more information on this type of change.

UVG Versions 3.x

Issues

The 3.x versions of UVG contain a different version of the NeatUpload module.  The advice given for 2.x versions will result in a 404 error appearing for any 'postback' link on your site, such as a login or register link.  The default install of UVG will result in an error when a video is uploaded.  This will show up as an exception, which you may or may not see in the browser, depending on error configuration.  You may find the exception listed as a 'warning' in the Windows Event Log, listed under ASP.NET.

The exception will look like this:

Event message: An unhandled exception has occurred. 
Exception information:
    Exception type: NullReferenceException
    Exception message: Object reference not set to an instance of an object. 
 
Thread information:
    Thread ID: 20
    Thread account name: NT AUTHORITY\NETWORK SERVICE
    Is impersonating: False
    Stack trace:    at Brettle.Web.NeatUpload.Internal.Module.FilteringWorkerRequest.ParseMultipart()
   at Brettle.Web.NeatUpload.Internal.Module.FilteringWorkerRequest.GetKnownRequestHeader(Int32 index)
   at System.Web.HttpRequest.FillInHeadersCollection()
   at System.Web.HttpRequest.get_Headers()
   at System.Web.Configuration.BrowserCapabilitiesFactoryBase.GetHttpBrowserCapabilities(HttpRequest request)
   at System.Web.Configuration.HttpCapabilitiesEvaluator.EvaluateFinal(HttpRequest request, Boolean onlyEvaluateUserAgent)
   at System.Web.Configuration.HttpCapabilitiesEvaluator.Evaluate(HttpRequest request)
   at System.Web.Configuration.HttpCapabilitiesBase.GetBrowserCapabilities(HttpRequest request)
   at System.Web.HttpRequest.get_Browser()
   at System.Web.HttpCookie.SupportsHttpOnly(HttpContext context)
   at System.Web.HttpCookie.GetSetCookieHeader(HttpContext context)
   at System.Web.HttpResponse.GenerateResponseHeadersForCookies()
   at System.Web.HttpResponse.UpdateNativeResponse(Boolean sendHeaders)
   at System.Web.HttpRuntime.FinishRequestNotification(IIS7WorkerRequest wr, HttpContext context, RequestNotificationStatus& status)
 

Configuration

There are two ways to correct the issues with the NeatUpload component.

- If you comment out the 'NeatUpload' entry (only in the <modules> list, not elsewhere in the config file) then you can upload videos successfully, though you lose the "progress bar" functionality when uploading videos.

- if you add 'allowDebugCode="true" attribute to the <add name="iFinity.UrlMaster" type="iFinity.DNN.Modules.UrlMaster.DNNFriendlyUrlProvider, (etc).. /> you can leave in the NeatUpload component. You must also move the NeatUpload component configuration entry below the UrlRewrite configuration entry, like this:

IIS7

<system.webserver>
<modules>
 <add name="UrlRewrite" type="iFinity.DNN.Modules.UrlMaster.UrlRewriteModule, iFinity.UrlMaster.FriendlyUrlProvider" preCondition="managedHandler" />
  <add name="UploadHttpModule" type="Brettle.Web.NeatUpload.UploadHttpModule, Brettle.Web.NeatUpload" preCondition="managedHandler" />
 

IIS6    

<system.web>
<httpModules>
<add name="UrlRewrite" type="iFinity.DNN.Modules.UrlMaster.UrlRewriteModule, iFinity.UrlMaster.FriendlyUrlProvider" />
 <add name="UploadHttpModule" type="Brettle.Web.NeatUpload.UploadHttpModule, Brettle.Web.NeatUpload" />
     




 |  View Topic History  |