ansaurus

Question

Master pages -- Getting calling page name

Answer 1

A:

Just use the "Page" member of the masterpage

spmason 2009-06-08 22:14:10

Answer 2

+1 A:

This is a similar question to what you're asking, but I would pay attention to the accepted answer, trying to figure out the child page from the master page is probably not a good design idea.

Brandon 2009-06-08 22:14:38

Well actually, what I'm trying to do is not change anything on either pages. What I want to do in the master page is check for a session variable, which holds login info, and if the variable is not set, I wanted to redirect to a login page. I wanted to page a RefPage variable in my querystring though that holds the URL of the previous page, that way, after the user logs in, I can refer them back to the original page

icemanind 2009-06-08 22:55:42

Answer 3

+1 A:

I would notify in the other direction. Add properties to your master page then set them from the content pages.

In your master:

public partial class PortalMaster : System.Web.UI.MasterPage
{

    public string PageSection { get; set; }
}

In your .aspx add this directive:

<%@ MasterType VirtualPath="PortalMaster.master" %>

Then in your .aspx.cs set the property value like so:

Master.PageSection = "about";

John Sheehan 2009-06-08 22:15:35

Well actually, what I'm trying to do is not change anything on either pages. What I want to do in the master page is check for a session variable, which holds login info, and if the variable is not set, I wanted to redirect to a login page. I wanted to page a RefPage variable in my querystring though that holds the URL of the previous page, that way, after the user logs in, I can refer them back to the original page

icemanind 2009-06-08 22:55:33

On your log in page, check for Request.UrlReferrer. If it has a value (not null), store it in a hidden input, then redirect after log in. No querystring needed.

John Sheehan 2009-06-09 04:18:01

Answer 4

A:

From the codebehind in the MasterPage, the Page.AppRelativeVirtualPath property will tell you the path.

ichiban 2009-06-08 22:18:40

Answer 5

+1 A:

Going with your comments, I see a couple of options:

1) In your login page, on a non-postback, check the Referrer - this will be the page that sent you to the login page (Request.UrlReferrer), store that in session for the postback of their login details, and then send the user back.

2) Use the standard features of ASP.NET to handle login/redirections (which basically use the same system as 1).

Zhaph - Ben Duguid 2009-06-08 23:12:43

ansaurus

tags:

views:

answers:

Master pages -- Getting calling page name

related questions