Hi I am seeking something like this where there is one fixed billing profile which can be updated via a tab in the user profile. It's for a subscription product although I haven't even begun to look at the subscription contrib module for commerce.
One thing I just discovered is that I'm unable to uninstall this module as it's stating dependency on fields, specifically on modules list:
Required by: Drupal (Field type(s) in use - see Field list)
Can you reassure me on the best way to disable the module? i.e.. delete the addressbook_saved_profiles field from the billing profile? Will there be any residue on the database or in fields that I should be aware of after disabling?
I realize this is in the beginning stages so I'm requesting support to do a clean uninstall.
Thanks
Comment | File | Size | Author |
---|---|---|---|
#9 | 1311470-uninstall.patch | 1.59 KB | bojanz |
#5 | 1311470-uninstall.patch | 1.59 KB | bojanz |
#4 | 1311470-uninstall.patch | 1.59 KB | bojanz |
Comments
Comment #1
blasthaus CreditAttribution: blasthaus commentedComment #2
blasthaus CreditAttribution: blasthaus commentedFollowing up here based on a better understanding of how fields work.
A helpful post here describing the same issue (but with different modules) can be found here http://drupal.org/node/1284332
More specifically this is the recommended approach Field types should be defined by one module and implemented by a separate module.
Notes on how to disable the module:
Suggestion: implement a simple uninstall function which integrates into the development of the module(s).
Comment #3
svendecabooterComment #4
bojanz CreditAttribution: bojanz commentedThe Addressbook 7.x-1.x branch created an interesting problem because it defines a field type AND creates instances of that type in the same module,
which is forbidden in newer Drupal releases (but probably wasn't at the time the code was written).
Here's a patch that should enable uninstall. It's completely untested.
Can someone with a 7.x-1.x install test?
Comment #5
bojanz CreditAttribution: bojanz commentedUse this one instead, the commerce_delete_fields() parameter was wrong.
Comment #6
kiwimind CreditAttribution: kiwimind commented@bojanz, thanks for the info. Just trying to finish off the issue I posted #1418518: Remove address dropdown when editing a customer's order.
I've got a couple of issues though...
1) I presume that the disable function name needs to be "function commerce_addressbook_disable", not "function commerce_addressbook_enable".
2) Even with this rename, I am unable to disable the module due to dependencies, which stops me from uninstalling it (as far as I'm aware).
Comment #7
bojanz CreditAttribution: bojanz commentedYeah, it needs to be commerce_addressbook_disable() or commerce_addressbook_uninstall().
The code is untested (didn't have time to follow it though), so it might need additional tweaks. I'll look into it after DrupalCon if nobody does it before then.
Comment #8
kiwimind CreditAttribution: kiwimind commentedOk, cool. Thanks.
Have a great time in Denver.
Comment #9
bojanz CreditAttribution: bojanz commentedRerolled to fix:
Don't have time to push this further right now. The patch should either work or be very very close.
Comment #10
bojanz CreditAttribution: bojanz commentedNevermind, we have an upgrade path to 2.x now.
Comment #11
kiwimind CreditAttribution: kiwimind commentedAwesome, thanks, will look at testing the upgrade instead of persuing this.