This is a fairly big feature addition and one that will only be exposed via a configuration setting in the Merchello.config file due to the fact we want to use the Umbraco Membership rather than forcing a "Merchello Customer/Member" on the Umbraco instance.
This update will include some refactoring of the CustomerContext to identify if a user is authenticated and behind the scenes manage the Anonymous Customer / Customer concerns, including conversion to/from conversions of anonymous customer to customer transitions due to authenticating at various points in shopping and checkout work flow.
Persisted Customers are also tied to payments and invoices so that invoicing, payments and order histories can be established.
Upgrade
After reviewing Umbraco 7.1 we already know that we are going update the merchCustomer table to remove the memberId in exchange for a string (either username or email address) as the tie to Umbraco Membership. There will also likely be some changes to the CustomerAddress structures in the database.
Clean up
We expect to have feedback from people building gateway providers and using the Notification / Reporting services.
Merchello 1.2.0
Merchello 1.2.0
Release Date: TBD
Persisted Customers
This is a fairly big feature addition and one that will only be exposed via a configuration setting in the Merchello.config file due to the fact we want to use the Umbraco Membership rather than forcing a "Merchello Customer/Member" on the Umbraco instance.
This update will include some refactoring of the CustomerContext to identify if a user is authenticated and behind the scenes manage the Anonymous Customer / Customer concerns, including conversion to/from conversions of anonymous customer to customer transitions due to authenticating at various points in shopping and checkout work flow.
Persisted Customers are also tied to payments and invoices so that invoicing, payments and order histories can be established.
Upgrade
After reviewing Umbraco 7.1 we already know that we are going update the merchCustomer table to remove the memberId in exchange for a string (either username or email address) as the tie to Umbraco Membership. There will also likely be some changes to the CustomerAddress structures in the database.
Clean up
We expect to have feedback from people building gateway providers and using the Notification / Reporting services.
Bugs
is working on a reply...