Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • overflew 87 posts 110 karma points
    Nov 01, 2010 @ 00:08
    overflew
    0

    Root node showing as logged out?

    Hi all,

    I have an Umbraco 4.5.2 site which has authenticated sections for 'members'.

    The issue I'm having is that when viewing the frontend site with the root URL (e.g. [site].com/), It shows the site as unauthenticated (when actually logged in). Clicking through to any other page (including the same root page via it's full url - [site].com/home.aspx) shows the user as logged in.

    The two visibly affected page controls are the navigation menu, and the "You are logged in / not logged in" control in the header.

    Site structure:

    Content
      - Home
        - Auth section 1
        - Auth section 2
        - Public section 1
        - Public section 2

    Nav XSLT snippet:

     

    <xsl:if test="umbraco.library:HasAccess(@id,@path) = 1">
      <xsl:if test="umbraco.library:IsLoggedOn() = 1">

    "You are logged in as" user control determines its status with a call to:

    protected override void OnPreRender(EventArgs e)
        {
            [...]
            var isLoggedIn = Request.IsAuthenticated;

    To summarize: When logged in as a member,

    • site.com/ - Shows as unauthorized
    • site.com/home.aspx - Shows as authorized
    And both are the same page. Any ideas on how it's determining this incorrectly, and how I can work around it?
    Cheers.

     

  • overflew 87 posts 110 karma points
    Nov 04, 2010 @ 00:55
    overflew
    0

    Hmmm, still no luck...

    Can anyone point me in the direction of where Umbraco's URL-rewriting is occurring? I see that I can add things in urlrewriting.config, but that seems a place for additional rewriting - not the base Umbraco stuff... - I figure this is one place to look...

     

  • Sean Mooney 131 posts 158 karma points c-trib
    Nov 04, 2010 @ 13:18
    Sean Mooney
    0

    I ran into this problem as well. Make the following change to the web.config file

    Change:

    <modules>

    To this:

    <modules runAllManagedModulesForAllRequests="true">

     

    -Sean

     

  • overflew 87 posts 110 karma points
    Nov 04, 2010 @ 21:38
    overflew
    0

    Absolute genius - Thanks Sean.

Please Sign in or register to post replies

Write your reply to:

Draft