Hi folks,
One of the stores I'm working on just developed an odd problem. It only happens if you log in to an account, say "Customer A;" go part way thru checkout, then log out, and log back in as Customer B. Everything looks fine until you go to checkout. Then, on the OCST page, Customer A's info shows up, even though you're now logged in as someone else.
I took a look at the DB, and I see that the problem is apparently caused by the customfields module. It's saving a copy of the entire basket status, including the customer ID, into the BasketInfo table. Once that info has been saved, it doesn't get deleted when you log out; and it doesn't get changed when you log back in. And when you get to OCST, this saved info is used to fill in all the fields, instead of the actual info for the account that you're currently logged in to.
After looking at the customfields module source code in the LSK, I gather that this behavior is triggered by a couple of mvt:item tags. The module creates the BasketInfo when rendering OSEL, and reads it when rendering OCST. It looks like these tags are part of the Suivant theme. Is this a Suivant bug? It seems strange for the read operation to occur before the write.
Thanks --
One of the stores I'm working on just developed an odd problem. It only happens if you log in to an account, say "Customer A;" go part way thru checkout, then log out, and log back in as Customer B. Everything looks fine until you go to checkout. Then, on the OCST page, Customer A's info shows up, even though you're now logged in as someone else.
I took a look at the DB, and I see that the problem is apparently caused by the customfields module. It's saving a copy of the entire basket status, including the customer ID, into the BasketInfo table. Once that info has been saved, it doesn't get deleted when you log out; and it doesn't get changed when you log back in. And when you get to OCST, this saved info is used to fill in all the fields, instead of the actual info for the account that you're currently logged in to.
After looking at the customfields module source code in the LSK, I gather that this behavior is triggered by a couple of mvt:item tags. The module creates the BasketInfo when rendering OSEL, and reads it when rendering OCST. It looks like these tags are part of the Suivant theme. Is this a Suivant bug? It seems strange for the read operation to occur before the write.
Thanks --
Comment