Portal integration updates #36
Conversation
| <h3 class="text-xl font-medium mb-4">@Umbraco.GetDictionaryValueOrDefault("UmbracoCommerceCheckout.Information.ContactInformation", "Contact Information")</h3> | ||
| <input name="email" type="email" placeholder="@Umbraco.GetDictionaryValueOrDefault("UmbracoCommerceCheckout.Information.Email", "Email")" class="block placeholder-gray-700 border border-gray-300 rounded py-2 px-4 mb-2 w-full" | ||
| value="@(currentOrder.CustomerInfo.Email)" required /> | ||
| value="@(customer.Email ?? currentOrder.CustomerInfo.Email)" required /> |
There was a problem hiding this comment.
For all properties the order should be first and fallback to the member properties. If the member properties are first then if they change these and progress in the checkout flow but then come back it will revert their changes back to the member properties. We only want to use the member properties if the order properties aren't yet populated.
There was a problem hiding this comment.
Updated. Used an extension method to pass the customer information as fallback.
| // This extension method should not be used in a context where order is null. | ||
| ArgumentNullException.ThrowIfNull(order); | ||
|
|
||
| return new CustomerAddress( |
There was a problem hiding this comment.
Might just need to double check if we should handle "shippingSameAsBilling" here and return the billing details if true.
|
|
||
| var customer = currentOrder.GetCustomer(orderPropertyConfig); | ||
| var billingAddress = currentOrder.GetBillingAddress(orderPropertyConfig); | ||
| var shippingAddress = currentOrder.GetShippingAddress(orderPropertyConfig); |
There was a problem hiding this comment.
Check if shipping address is being captured (a setting in the checkout) and if not, we don't need to get the details.
Current PR adds support for an authorized checkout flow with the following additional features implemented:
Checkoutpage to specify whether login is required, and specified the login content node. If login is required but no login page has been specified, the action result will beUnauthorized.Using the
Checkoutadd-on in parallel with thePortalone, upon login the customer will be automatically assigned to the current order.FYI @umbracotrd