Modules routing returns blank output, wtf!

Luc Gosso (MVP)

Vote:

Hello Experts,

Latest version 11.12 CMS

I´ve set up a new site but no modules routes are working.

not /EPiServer/Cms/VisitorGroups

not /EPiServer/EPiServer.DeveloperTools/IOC

not /EPiServer/EPiServer.GoogleAnalytics/Administration

Just blank no html output

I do get to login before though

What can it be?

I do use feature folder setup, but thats just a simple change in DefaultPageController.

#202237

Mar 20, 2019 12:53

Quan Mai

Vote:

A routine question: do you see anything in the browser console?

#202238

Mar 20, 2019 13:49

Eric Petersson

Vote:

I know that for some certain routes you have to specify default.aspx as content output

For instance /EPiServer/cms/admin/ does not return the admin view but /EPiServer/cms/admin/default.aspx does.

This should however not be part of your problem...

#202242

Mar 20, 2019 16:03

Vote:

Nada in Console.

Nada in log file.

/default.aspx makes it throw 404 "A public action method 'default.aspx' was not found on controller 'EPiServer.Cms.Shell.UI.Controllers.Internal.VisitorGroupsController'."

/index = empty blank

Something is killling it softly, it probably something stupido.

#202260

Mar 21, 2019 9:55

Mattias Olsson

Vote:

How does your <episerver.shell> and <location path="EPiServer"> configuration look like in Web.config?

#202263

Mar 21, 2019 10:16

Vote:

Looks good Mattias, compared with working sites and no diff.

#202266

Mar 21, 2019 10:44

Mattias Olsson

Vote:

File system access rights? :)

#202268

Mar 21, 2019 10:51

Vote:

Full access no diff.

I have same behavior on staging server, so its not just local.

Have i Messed up SiteViewEngine : RazorViewEngine? i don't find anything there too though

#202269

Mar 21, 2019 11:01

valdis

Vote:

hos does your RouteTable look like?

#202276

Mar 21, 2019 16:50

Vote:

The RouteTable looks as good as you do Jedi Master Iljuconoks.

39 items.

you have items like

{[ModuleRouteCollection RoutePath="~/EPiServer/EPiServer.GoogleAnalytics/2.1.1", Routes=[EPiServer.GoogleAnalyticsepi-googleanalytics]]}

{[ModuleRouteCollection RoutePath="~/EPiServer/EPiServer.DeveloperTools", Routes=[]]}'

{[ModuleRouteCollection RoutePath="~/episerver", Routes=[EPiServer.Packaging.UI,EPiServer.Search.Cms,AddOn.Edit.ContextMenuOpenInNewTab,EPiServer.DeveloperTools,Shell,CMS,EPiServer.Cms.TinyMce,EPiServer.Forms.UI,EPiServer.Forms,EPiServer.GoogleAnalytics]]}

What more should i be looking for?

#202298

Mar 22, 2019 10:16

Quan Mai

Vote:

If you reach out for developer support service for this, I would be happy to look into this :)

#202299

Mar 22, 2019 10:19

Vote:

Cred to Episerver Dev Support,

After debugging Episerver Source they found out the root cause of this issue is SiteViewEngine is inserted to ViewEngines in the first position:

ViewEngines.Engines.Insert(0, new SiteViewEngine()); // which is default in alloy template to optimize view resolving when using DisplayFor/PropertyFor

So it overrides the episerver ViewEngine.
You can use this instead of:

ViewEngines.Engines.Add(new SiteViewEngine());

We did made some customization in viewengine so maybe not so suprising.

Regards

#202998

Apr 05, 2019 15:05

Quan Mai

Vote:

Hey I deserve a bit of credit as well ;) (telling you to reach out for Dev support)

#202999

Apr 05, 2019 15:10

Mattias Olsson

Vote:

To tweak view resolving a little bit, you could insert it right before WebFormViewEngine (if using default MVC setup):

var webFormViewEngine = ViewEngines.Engines.FirstOrDefault(ve => ve.GetType() == typeof(WebFormViewEngine));

if (webFormViewEngine != null)
{
    var webFormViewEngineIndex = ViewEngines.Engines.IndexOf(webFormViewEngine);
    
    ViewEngines.Engines.Insert(webFormViewEngineIndex, new SiteViewEngine());
}
else
{
    ViewEngines.Engines.Add(new SiteViewEngine());
}

#203105

Apr 09, 2019 12:42