Thanks for the support, everyone!

Posts: 29
Joined: 05/06/2008

Hi, everyone. Thanks for the kind words and encouragement.

Some responses: Ablinet likes the term "recipient" instead of "addresses". I started with Amazon as a model: if it works for them, it probably works. They use the terms "address book" and "addresses". These "addresses" include a name and a phone number. Also, "recipient" doesn't make sense for the billing address. So I think I will stick with the current terminology.

Albinet wrote:
EDIT: I quickly tested this module a it really looks promising (the only confusing thing was, I'm now really selecting from "addresses" without a clear indication, to whom the delivery in question is actually going to) ...once again, thinking about a gift shop from the gift buyers point of view (one shopping session, selecting multiple gifts, every gift can have a different recipient with different delivery address)

If I understand this correctly, the problem is that each order can only have one recipient. I hadn't really noticed this limitation of Ubercart (I'm new to Ubercart), but I believe this is a limitation of the order system and not of the addresses module. It's quite possible I'm missing something, so please let me know.

72dpi wrote:
I assume this hooks in perfect with the Postage module? (i am using Auspost).

I'll confess that I have no idea if it hooks in with the Postage module. The way that the order system handles addresses is unchanged except that you select addresses from the user's address book rather than from previous orders. That's it. 72dpi, let me know if you find any problems.

greenSkin wrote:
Concerning recipients vs addresses, generally addresses don't change where as recipients change addresses so I believe the decision on should be based on whether or not you want to organize the addresses/recipients by person or address.

In most address books, including the one in the uc_addresses module, you can edit both the name and the address. So, does this make it a recipient or an address?

Rich, thanks specially for your support. Indeed, when working on Drupal, we are all stepping on the shoulders of giants.

I look forward to hearing about any problems. I noticed one bug myself: When you first register, the form does not include the "Default address" option (whatever you enter becomes the default). When I removed the option from this form, I also removed this from the "Add a new address" form since it turns out that these two are handled by the same code. I will add it back.

Also, if you edit the default address, the "Default address" option is on. Turning it off does not make the default address not be the default address since there is always a default address. I should probably disable the option when editing the default address to avoid confusion.

A bigger question is whether there is a need for a default address and how it should be used. Amazon also has the concept of a default address. They use it for 1-Click ordering. Maybe the shipping address should automatically be filled with the default address? Or the billing field? Or both? Right now, the customer doesn't see anything special about the default address--it's just the address the store owner should look at when trying to contact the customer, but this is not enforced anywhere.

Suggestions?

Storing Address information in User Profile By: bendiy (74 replies) Thu, 10/25/2007 - 19:04