User loginRecent blog posts
|
more Membership questionsI have an app that users may or may not be logged into and will select a product, that then redirects into Storefront to complete the selection and purchase of the product. Both MyApp and Storefront point to the same aspnet tables. Therefore, if the user logs in to MyApp, then goes to Storefront, Storefront sees them as logged in... but not entirely. I've confirmed that somehow ZNodeUserAccount.CurrentAccount() returns the logged in account, but it doesn't get into the Session, so that when the user goes to the checkout page, they get bounced to the login page. I'm thinking that I can add code to the page that we always go in on (product.aspx) to take the CurrentAccount and add it to the Session object, but I'm afraid of any side effects. For the same reason, I'm reluctant to take out the check in Checkout.aspx for the ZNodeUserAccount. So much of this stuff seems to be in ZNode.Libraries.Framework.Business and therefore hidden.
|
SearchQuick Links |
After putting the
After putting the CurrentUser on the Session in Product.aspx, I find that while the *name* of the user is the name of the current membership user, the other information in the object (profile stuff, billing, shipping addrs) is from the *last* logged in user. Not good.
Is there some way to "synchronize" the currently logged in membership user and get back the correct ZNodeUserAccount?