I want to use members in my "Umazel site".
Following the tutorial I started creating a Register Page a Login Page and a Login Status Macro, using the macros already present in Umbraco on a development local installation based on Umbraco 8.12.2 and Umazel Package 2.0.
I’ve put the login-status macro in the menu using Umbraco.RenderMacro instead of Html.Partial.
When I open the registration page the fields are pre-filled with the credentials of the user. If I register a new member the “login status” in the navigation bar works properly.
I then log out using the logout button (there is no confirmation except the login status changes).
If I try to log in again I get the following error.
If the same tutorial is used on an empty Umbraco installation it works perfectly.
Do you have any hint?
Thanks in advance.
The provided anti-forgery token was meant for user "[email protected]", but the current user is "".
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Web.Mvc.HttpAntiForgeryException: The provided anti-forgery token was meant for user "[email protected]", but the current user is "".
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[HttpAntiForgeryException (0x80004005): The provided anti-forgery token was meant for user "[email protected]", but the current user is "".]
System.Web.Helpers.AntiXsrf.TokenValidator.ValidateTokens(HttpContextBase httpContext, IIdentity identity, AntiForgeryToken sessionToken, AntiForgeryToken fieldToken) +838
System.Web.Helpers.AntiXsrf.AntiForgeryWorker.Validate(HttpContextBase httpContext) +128
System.Web.Mvc.ControllerActionInvoker.InvokeAuthorizationFilters(ControllerContext controllerContext, IList1 filters, ActionDescriptor actionDescriptor) +168
System.Web.Mvc.Async.<>c__DisplayClass3_1.<BeginInvokeAction>b__0(AsyncCallback asyncCallback, Object asyncState) +1082
System.Web.Mvc.Async.WrappedAsyncResultBase1.Begin(AsyncCallback callback, Object state, Int32 timeout) +163
System.Web.Mvc.Async.AsyncControllerActionInvoker.BeginInvokeAction(ControllerContext controllerContext, String actionName, AsyncCallback callback, Object state) +463
System.Web.Mvc.<>c.
Working with Members
Hi All,
I want to use members in my "Umazel site". Following the tutorial I started creating a Register Page a Login Page and a Login Status Macro, using the macros already present in Umbraco on a development local installation based on Umbraco 8.12.2 and Umazel Package 2.0. I’ve put the login-status macro in the menu using Umbraco.RenderMacro instead of Html.Partial. When I open the registration page the fields are pre-filled with the credentials of the user. If I register a new member the “login status” in the navigation bar works properly.
I then log out using the logout button (there is no confirmation except the login status changes). If I try to log in again I get the following error. If the same tutorial is used on an empty Umbraco installation it works perfectly.
Do you have any hint?
Thanks in advance.
The provided anti-forgery token was meant for user "[email protected]", but the current user is "". Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Web.Mvc.HttpAntiForgeryException: The provided anti-forgery token was meant for user "[email protected]", but the current user is "".
Source Error: An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[HttpAntiForgeryException (0x80004005): The provided anti-forgery token was meant for user "[email protected]", but the current user is "".] System.Web.Helpers.AntiXsrf.TokenValidator.ValidateTokens(HttpContextBase httpContext, IIdentity identity, AntiForgeryToken sessionToken, AntiForgeryToken fieldToken) +838 System.Web.Helpers.AntiXsrf.AntiForgeryWorker.Validate(HttpContextBase httpContext) +128 System.Web.Mvc.ControllerActionInvoker.InvokeAuthorizationFilters(ControllerContext controllerContext, IList
1 filters, ActionDescriptor actionDescriptor) +168 System.Web.Mvc.Async.<>c__DisplayClass3_1.<BeginInvokeAction>b__0(AsyncCallback asyncCallback, Object asyncState) +1082 System.Web.Mvc.Async.WrappedAsyncResultBase
1.Begin(AsyncCallback callback, Object state, Int32 timeout) +163 System.Web.Mvc.Async.AsyncControllerActionInvoker.BeginInvokeAction(ControllerContext controllerContext, String actionName, AsyncCallback callback, Object state) +463 System.Web.Mvc.<>c.Sounds like you have a cached version of the login form
is working on a reply...