iFinity

Ok, I have successfully replicated your problem (either creating a 404 error - neatupload at top of modules list) or getting 'object reference not set' error if NeatUpload is below UrlRewrite in the list.

Here's the scenarios:

- if you put NeatUpload above the Url Rewrite entry in the list (as previous advice has been) then you'll get a 404 on every postback from your site (including login links, video uploads, etc)

- if you move NeatUpload below the Url Rewrite entry in the modules list, then you get a 'object reference not set to instance of object' exception, like this (it may or may not show up in the browser, depending on your web.config error settings)

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)
 
- If you comment out the 'NeatUpload' entry (only in the <modules> list, not elsewhere in the config file) then you can upload videos successfully.  I'm not sure where the NeatUpload component works in this case : perhaps I need to upload a larger video to get it to show.

- if you add 'showDebugCode="true" attribute to the <add name="iFinity.UrlMaster" type="iFinity.DNN.Modules.UrlMaster.DNNFriendlyUrlProvider, (etc).. /> you can leave in the NeatUpload component (as long as it appears under the UrlRewrite entry in the web.config list).  Note I gave incorrect advice earlier in this thread - advising 'showDebug' instead of 'showDebugCode' - my own documentation was incorrect on this, which I have now fixed.

I will contact the author of the NeatUpload component and see what has changed and if it's possible to get a fix in place, or any other advice.

My advice currently is to add the 'showDebugCode="true"' into the Url Master config entry.  This should result in everything working as expected.

What is the error on login?  Do you get a 404 error, or is it something else? Is the error different for each position of the entries in the modules list?  In my testing, I get a 404 error on posbacks (such as clicking on the login link) if the NeatUpload component precedes the UrlRewrite entry.  If the NeatUpload component is after the UrlRewrite entry, then I would see a 'object not set' exception logged.  Is that what you are seeing?