It would be better, too, if this field were managed by Ubercart core, as well.

Could easily be controlled with a role permission.
At the very least, this would be handy to disable for, say, companies that sell B2B and want users to create "wishlists" of products for quotes or other purposes.

Comments

HumanTex’s picture

HumanTex CreditAttribution: HumanTex commented

+1 on this too.

Just going through testing on a dev setup for this and found it was mandatory within the module. As I won't be selling physical products - only downloadable files - so there is no need for delivery addresses at any level in my case.

Addresses may be part of the 3rd party purchaser's setup for billing/verification, but not for the recipient of that purchase, nor is it needed for the sake of saving a product list for the user's own purchases at a later time. They still have to enter their address info to become a valid customer for payments prior to their first purchase... so this becomes redundant and not necessary for their own personal use.

If there needs to be a requirement flag within the wishlist module itself, it might be better to verify it's needed for a physical/deliverable item first, and/or have it flag the order to have those fields as "must be completed" before it can become a finalized order and shipped (by entry of either the recipient or the 3rd party purchaser, if they have the address info). Without the fields being complete it would just be marked as a pending order - plus - not trigger any billing action until they're completed.

ColinMctavish’s picture

ColinMctavish CreditAttribution: ColinMctavish commented

+1

naveenvalecha’s picture

naveenvalecha
He/Him
Primary language Hindi
CreditAttribution: naveenvalecha as a volunteer and at Acquia commented
Issue summary: View changes
Status: Active » Closed (outdated)

Closing because Drupal 6 is no longer supported. If the issue verifiably applies to later versions, please reopen with details and update the version.