This project is read-only.
1

Closed

Blank State route is ignored

description

Currently a blank route attribute is considered the same as not specifying a route.

Should be able to specify a blank route against a State so that requesting the root url, e.g., site/ navigates to that State.

This feature has been mentioned in https://navigation.codeplex.com/discussions/450128 and https://navigation.codeplex.com/discussions/540235
Closed Apr 25, 2014 at 11:23 PM by GrahamMendick

comments

GrahamMendick wrote Apr 25, 2014 at 11:23 PM

The blank/root route can be configured using ~
<state key="Listing" page="~/Listing.aspx" route="~">
</state>
This is fixed by changeset 21e8adbeb891

engerdude wrote May 12, 2014 at 10:51 PM

Hi Graham,

I wondered if a problem I am having is related to configuring a blank/root route.

I recently changed my default page (defaultDocument in web.config) to go to /Account/Login.aspx (the AspNet.Identity application). When a user enters the website specifying the name /Account/Login in the url it works fine. If they do not specify a page, they get a ' Navigation.UrlException: The Url is invalid' message.

The url displayed starts with the query parameters '?c0=3-0' after the website name.

Best Regards.

GrahamMendick wrote May 13, 2014 at 6:34 PM

How is your app set up? Are you using my Navigation Identity Sample or the VS template? Have you disabled FriendlyUrls (see Issue #3)?

Why not configure your default page to be /Account/Login instead of /Account/Login.aspx? Wouldn't that do the trick?

If you're still stuck send me some more information, but I think it's best to start up a separate discussion.

Cheers,
Graham

GrahamMendick wrote May 16, 2014 at 5:34 PM

Hi @engerdude, have you had any luck with your issue? I'm happy to help if you send me some more info.