New report: Tree Presentation URLs Analysis

[yuriys-kentico]

Motivation

It is difficult to know which pages in the tree are routed to which controllers.

Proposed solution

I want to see a table of NodeAliasPath, the generated route, and matching controller.

Additional context

I realize this could get very complex due to the need to resolve macros and parse a route table, nevermind dynamic constraints on routes.

[JosefDvorak]

Thanks for the suggestion, Yuri.

At first glance, this could be fairly hard to implement, since each project could be using different routing. You could test every NodeAliasPath against running application, and somehow see which Controller / View is hit. Have you come across any tool or library that would help with this? I suspect .NET MVC will have something for this kind of testing.

Another issue could be that a node in Kentico does not necessarily relate to a Page in MVC site. I.e., in the most extreme example, there could be MVC Pages that are composed of multiple node data, which have URLs completely independent of Kentico node hierarchy. That being said, some reporting is better than no reporting.