I have a user control which has a public member, through which I pass a pageId. The user control then tries to get the url of the page for the purpose of a redirect. However, both NiceUrl functions seem to be returning funny values:
When I was expecting ~/Student/Dashboards.aspx and /schools/vle/students/dashboard respectively.
The site is running in a virtual directory called 'schools', and my root node also called 'schools' (but this shouldn't show in the url right?). I'm using version Umbraco 4.5.
Ok. Just a problem our end. NiceUrl is working absolutely fine. My public property was a int? which was preventing the value being passed in and it was then falling back to a default value from our dev environment. Changing it to int then works fine.
NiceUrlFullPath works as it is supposed to, adding in the root node in to the path. No idea why you'd want this, but there is no fault here. Apologies.
NiceUrl/ NiceUrlFullPath acting out
I have a user control which has a public member, through which I pass a pageId. The user control then tries to get the url of the page for the purpose of a redirect. However, both NiceUrl functions seem to be returning funny values:
NiceUrl : ~/StudentDashboard.aspx
NiceUrlFullPath : /schools/schools/vle/students/dashboard.aspx
When I was expecting ~/Student/Dashboards.aspx and /schools/vle/students/dashboard respectively.
The site is running in a virtual directory called 'schools', and my root node also called 'schools' (but this shouldn't show in the url right?). I'm using version Umbraco 4.5.
Is this a bug?
Cheers,
David
Hmm... Just realised that the NiceUrl output mentioned above is not correct, and was being falsely output. I'll update once I've got a genuine output.
Ok. Just a problem our end. NiceUrl is working absolutely fine. My public property was a int? which was preventing the value being passed in and it was then falling back to a default value from our dev environment. Changing it to int then works fine.
NiceUrlFullPath works as it is supposed to, adding in the root node in to the path. No idea why you'd want this, but there is no fault here. Apologies.
is working on a reply...