The phone number of the shipping address is not saved anymore with Merchello 2.1.
You can test it in the FastTrack: Buy something add billing address add shipping address (and phone) click next choose payment/shipping GO BACK and then you see that the phone of the shipping is not saved anymore!
This looks like an error in the FastTrack starter kit. The intent was to show that different models could be used for the Shipping and Billing addresses and I should have removed the phone field from the shipping address form (view) for the example. Missed that.
If you want to use the shipping address phone number, you can create your own CheckoutAddressController based off the one in fast track and change out the shipping address model in the controller abstract.
Then override the factory for the CheckoutAddressFactory with one that assigns the phone number by overriding the OnCreate methods.
I'll also have a look to make sure it's cleaned up.
The address should be saved in the Customer extended data (legacy XML) - can you check the persisted value before and after - maybe it's a retrieval problem but I've not encountered that one before.
Can you also verify that I'm reading this correct in that the bulk of the shipping address is there, it's just the phone number that is missing ...
Yes everything is saved except the phone number. It's only missing in the shipping address (billing address works) so thats probably why no one noticed ;-).
So when you retrieve the shipping (IAddress, XML) with GetShipToAddress() data like firstname, lastname, address, ... is there but the phone number is missing.
Yep - it's still there and on the Agile board for 2.3.0. May have to bump it back from 2.3.0 version to an unplanned 2.2.2 patch as 2.3.0 won't be out for a bit.
Merchello 2.1 Shipping Address Phone is not saved
Hi Rusty
The phone number of the shipping address is not saved anymore with Merchello 2.1.
You can test it in the FastTrack: Buy something add billing address add shipping address (and phone) click next choose payment/shipping GO BACK and then you see that the phone of the shipping is not saved anymore!
Thank you
Calvin
Hi Calvin,
This looks like an error in the FastTrack starter kit. The intent was to show that different models could be used for the Shipping and Billing addresses and I should have removed the phone field from the shipping address form (view) for the example. Missed that.
If you want to use the shipping address phone number, you can create your own CheckoutAddressController based off the one in fast track and change out the shipping address model in the controller abstract.
Then override the factory for the CheckoutAddressFactory with one that assigns the phone number by overriding the OnCreate methods.
I'll also have a look to make sure it's cleaned up.
Thanks for letting me know.
Hi Rusty
You probably misunderstood me.
I don't use FastTrack but have the same issue. Just tried to tell you how you can replicate the problem.
After SaveShipToAddress the pone is there but if you redirect it's gone!
Thanks
Calvin
The address should be saved in the Customer extended data (legacy XML) - can you check the persisted value before and after - maybe it's a retrieval problem but I've not encountered that one before.
Can you also verify that I'm reading this correct in that the bulk of the shipping address is there, it's just the phone number that is missing ...
Yes everything is saved except the phone number. It's only missing in the shipping address (billing address works) so thats probably why no one noticed ;-).
So when you retrieve the shipping (IAddress, XML) with GetShipToAddress() data like firstname, lastname, address, ... is there but the phone number is missing.
Thanks Calvin,
This gives me something to setup a few tests with ...
Hi Rusty
Do you have any updates about this bug?
Thanks
Calvin
Sorry Calvin - have not been able to get to that one yet. It's in the list though.
Hi Rusty
Tested with 2.2.1 and have still the error. So still on the list, right :-)?
Thanks
Calvin
Yep - it's still there and on the Agile board for 2.3.0. May have to bump it back from 2.3.0 version to an unplanned 2.2.2 patch as 2.3.0 won't be out for a bit.
If that is possible I would really appreciate it :-).
Hey Calvin,
I found the issue and will merge it into the v2.2.2 branch in a bit.
is working on a reply...