Just want to check I'm not missing something, does umbraco.library:GetCurrentMember() not work if you're using AspNetSqlMembershipProvider?
I've seen examples using the snippet below, but when I use this I get no CurrentMember, IsLoggedOn returns true but no member returned.
Should I be writing my own XSLT extension for this?
<xsl:choose> <xsl:when test="umbraco.library:IsLoggedOn() = true()"> You are logged in as <p> <xsl:variable name="user" select="umbraco.library:GetCurrentMember()/@loginName"/> <xsl:value-of select="$user"/> </p> </xsl:when> <xsl:otherwise> You are not logged in.
You'll have to write your own extension for it, umbraco.library doesn't use the MembershipProvider for accessing the member, it still uses the old API.
umbraco.library:GetCurrentMember with AspNetSqlMembershipProvider
Just want to check I'm not missing something, does umbraco.library:GetCurrentMember() not work if you're using AspNetSqlMembershipProvider?
I've seen examples using the snippet below, but when I use this I get no CurrentMember, IsLoggedOn returns true but no member returned.
Should I be writing my own XSLT extension for this?
<xsl:choose>
<xsl:when test="umbraco.library:IsLoggedOn() = true()">
You are logged in as
<p>
<xsl:variable name="user" select="umbraco.library:GetCurrentMember()/@loginName"/>
<xsl:value-of select="$user"/>
</p>
</xsl:when>
<xsl:otherwise>
You are not logged in.
</xsl:otherwise>
You'll have to write your own extension for it, umbraco.library doesn't use the MembershipProvider for accessing the member, it still uses the old API.
is working on a reply...