Martin Sanderson Please check the requirement here.
Matt Jones
•
Mar 4, 2020
Check that other eCommerce views will be available in workflow/autoresponders too. Gilbert and Daniel between them have 60 ecommerce sites blocked by this.
Matt Jones
•
Feb 27, 2020
This can be done very easily for logged in users. Simply in "userorders" use context.currentuser.id instead of currentuser.id which does not have correct pOS mapping in context of email. E.g. context.currentuser: {"firstname":"awdadw","lastname":"","email":"kokitap797@p5mail.com","id":"14769","slug":"awdadw"} current_user: UserDrop For Logged in Users- it may be possible to use email address instead.
Log in to comment and vote
Comments7
May 7, 2020
Released here -> https://help.siteglide.com/en/articles/4002657
Barbara Pearn
Jan 25, 2022
Matt Walter: This link doesn't work unfortunately.
Matt Walter
Jan 25, 2022
Barbara Pearn: https://help.siteglide.com/en/article/module-ecommerce-changelog-walfc7/#2-0120-7th-may-2020
Apr 21, 2020
kalyani
Mar 11, 2020
Martin Sanderson Please check the requirement here.
Matt Jones
Mar 4, 2020
Check that other eCommerce views will be available in workflow/autoresponders too. Gilbert and Daniel between them have 60 ecommerce sites blocked by this.
Matt Jones
Feb 27, 2020
This can be done very easily for logged in users.
Simply in "userorders" use context.currentuser.id instead of currentuser.id which does not have correct pOS mapping in context of email. E.g. context.currentuser: {"firstname":"awdadw","lastname":"","email":"kokitap797@p5mail.com","id":"14769","slug":"awdadw"}
current_user: UserDrop
For Logged in Users- it may be possible to use email address instead.