1
DocumentUltimate stops working when placed inside a DotNetNuke web.
Question asked by Chris Kleszynski - August 30 at 12:22 PM
Answered
Hello,
I am evaluating the DU for a client application based on DotNetNuke.
A simple test .aspx page with viewer and a .docx file works perfectly in its own web.
But as soon as I copy the file and the dlls to the dnn site and run the file it shows 404 error on loading js and css files from:
dnn.local/resource.ashx/636394628820000000/du/viewer.js 
dnn.local/resource.ashx/636394628820000000/du/viewer.css  
 
On both sites the view.aspx is placed directly in web root.

1 Reply

Reply to Thread
0
Cem Alacayir Replied
August 31 at 11:10 AM
Employee Post
You are getting HTTP 404 error because DotNetNuke takes over or clears the routes.
 
One customer solved it by adding this class:
 
using System.Text;
using System.Threading.Tasks;
using DotNetNuke.Web.Api;
using GleamTech.DocumentUltimate.Web;

namespace DabRegisterGleamTech
{
    public class RouteMapper : IServiceRouteMapper
    {
        public void RegisterRoutes(IMapRoute mapRouteManager)
        {
            DocumentUltimateWebConfiguration.RestoreRoutes();
        }
    }
}
Update: RestoreRoutes instead of PreApplicationStart method should be called.
 

Reply to Thread