I vote for having a dedicated table for user information like name, company, address, address name. The customers need to be able to edit the ship-to locations. Kinda like amazon :-/ Anonymous users could be allowed to create a wishlist similar to how they create a shopping cart, except they would see a "save wishlist" button to create a user account and save contact info.

I've finished an initial version of the wish list module, and I'd appreciate suggestions from the community on directions for future development.

To install it:
1. Download the uc_wishlist.tgz attachment to this comment.
2. Extract the contents into the Ubercart directory. (This will create a uc_wishlist subdirectory).
3. Patch uc_cart.module with included update: From the uc_cart directory, run patch -p0 < ../uc_wishlist/uc_cart.patch

This has been tested with Ubercart Alpha 7d, 7e, and a recent Bazaar version.

These are some issues that came up in development:

I wanted to make the module as self-contained as possible so that little patching of other Ubercart modules would be required. For example, I added the 'add to wish list' buttons next to the 'add to cart' buttons by altering uc_product_add_to_cart_form, catching the form, and resubmitting it if the intended operation was to add to cart. However to automatically add the recipient's address to the shopping cart checkout form, it seemed preferable to make a patch for uc_cart rather than creating an alternate handler.

The number of products purchased from a user's wish list is tracked through a uc_order hook. When an item is added to the shopping cart from a wish list, extra information (the wish list and wish list product id) is added to the data array. Then when an order is completed (when the order status becomes pending) the order is scanned for items that came from a wish list. If any are found, their corresponding wish list products are updated, adding the order id, order product id, user id, and timestamp to the purchase field in the wish list products table.

I would like to see a central way of handling and accessing address data. I had to leave a fair amount of panes, css, and js code from uc_cart behind to provide this module's own address interface.

The module introduces two new tables (schemas updated from above):

{uc_wishlists}
wid (int) -- wish list id
uid (text) -- user id or session id
title (text) -- wish list title
date (int) -- event date/deadline
address (text) -- delivery address

{uc_wishlist_products}
wpid (int) -- wish list product id
wid (int) -- wish list id
nid (int) -- product node id
qty (int) -- quantity wanted
changed (int) -- timestamp of last modification
data (text) -- serialized array of product attributes and data
purchase (text) -- serialized array of purchase records

A quick thought on the need for a patch... instead of doing that, you can really just use hook_form_alter() for the checkout form. If the conditions pass (no existing order - check $_SESSION['cart_order'] - and items only come from one wishlist), then set the default values to the address fields for the wishlist.

About the address handling, I've been thinking about this some more and would be open to discussing it if you started a thread in the development forum. I just don't have any good ideas on design/implementation at the moment. Well, I have some, I just don't know if they're good or not.

Off topic... the Sundays Energy equation grows larger and larger... I think next it should be broken down like so:

Sundays Energy = Drupal * Design + Drupal * Development + Drupal * Hosting + Ubercart * Design + Ubercart * Development + Ubercart * Hosting

But that wouldn't be quite so pretty. ^_^

We're on that discovery mission. Is there a Pi badge in the works for the ultimate equation?
Anyways, we're meeting with the client who will be using the registry next week with hopes of getting the site live within two weeks. Please keep us updated with any tests and/or suggestions.

CLiDE, I think you've described an important feature addition for the wish list module: customers should be able to send a link to their wish list through the store site.

I'll get this slated for one of the next updates, unless of course you want to dig around in the code and post a patch.

detour -- the wishlist module makes the Search Settings not work -- I've narrowed this error down to the Wish List Module:

Fatal error: Cannot use string offset as an array in /home/.zhukov/killerjerseys/killerjerseys.com/includes/form.inc on line 680

This error message has been driving me nuts all week! I trashed my drupal install because of it, lol. All is good, though

Also, the "Hide block if wish list is empty." option in the Block settings doesn't work.

I'm using version 0.4.

Otherwise, great work!

Joe, Is there a way that users can add products to the wish list that are not in the catalog. I think that would be helpful because in my case it becomes hard for the store to carry all variety of products..

thank you,

PS: Ubercart team great job.

Couple of issues (somewhat related):

1) I have added the wishlist module to our ubercart installation, it seems to work fine, except for one thing. Our store is 100% digital distribution - ie addresses are not required at all for purchasing items. Is there an easy way to disable the 'address requirement' that the wishlist seems to impose on users creating wishlists?

2) A secondary issue regarding wishlists, I have two countries enabled, canada and US - but when I try to select the Canada address and the a province, the wishlist 'submit' prompt tells me that I have selected an invalid entry and to contact the site administrator. The 'zone' listbox then reverts to US states, even though the country list selection remains on canada.

If I choose US and a state for my mailing address, it submits fine.

If I can figure out #1 (disabling the address requirement), then #2 is a non-issue, but I'm sure will arise for other users that DO care about having non-US addresses available in their stores.

Thanx in advance,