Hi,
I discovered some behaviour of Konakart that rather appears to be due to some bug:
1. If a user session is not terminated by performing a logout, then a different user logging in on the login page will inherit info of the previous user (basically, user is not refreshed after login). I consider this a serious issue regarding privacy!
2. In some cases we want to store different delivery/billing user info in the order, but not storing it as a new customer or address. So I made some customization to update user info in the order, however these modifications are not reflected in the checkout confirmation page (but does get saved in the DB), mostly because I guess the getFormattedAddress method doesn't use customer info from the order, but is hardwired to collect user info from user object and user's primary address. This behaviour seems to block some customization (I could display the correct data on checkout conf. page, but lost the formatting).
I hope this info helps to make Konakart an even better product.
I discovered some behaviour of Konakart that rather appears to be due to some bug:
1. If a user session is not terminated by performing a logout, then a different user logging in on the login page will inherit info of the previous user (basically, user is not refreshed after login). I consider this a serious issue regarding privacy!
2. In some cases we want to store different delivery/billing user info in the order, but not storing it as a new customer or address. So I made some customization to update user info in the order, however these modifications are not reflected in the checkout confirmation page (but does get saved in the DB), mostly because I guess the getFormattedAddress method doesn't use customer info from the order, but is hardwired to collect user info from user object and user's primary address. This behaviour seems to block some customization (I could display the correct data on checkout conf. page, but lost the formatting).
I hope this info helps to make Konakart an even better product.