I had lots of problems reinstalling Shipping due to a D7 bug (?).
To reinstall the module, I followed these steps (inspired by http://drupal.org/node/858722#comment-4467042 and some IRC #drupalcommerce chats) .

  • removed "events, conditions and actions" from "reaction rule Shipping example method" (because cannot delete the complete rule) and,
  • in shipping settings: disabled the "reaction rule Shipping example method" ,
  • disable "Shopping cart summary"-view
  • disable the module
  • uninstall the module
  • deleted the folder
  • update.php

Then I used the issue 858722 and searched for "shipping" and deleted the rows, here :

  • field_config (nothing)
  • field_config_instance (in bundle)
  • drop table if exists "shipping" in field_data_commerce_shipping_*
  • drop table if exists "shipping" in field_revision_commerce_*

Truncated:

  • cache_field
  • cache_bootstrap

don't forget to search for "shipping" in tables and values, and you may find:

  • field_data_shipping_method
  • field_revision_shipping_method

And there are also some rows to find, but you need to search well.

To finish I did again "update.php" and "drush cc all" .
Checked the site if it's not broken, if all rules etc. for shipping are gone.

Reinstalled the module.
I got the notice:
Notice: Undefined index: weight in field_info_max_weight() (line 799 of /var/www/pbcosmetics/modules/field/field.info.inc).

Again: Update.php

It would be lot easier if this could be done, just by "un-install" the module.

Comments

latulipeblanche’s picture

latulipeblanche commented

Use this as guide, but be careful because deleting too much can break your site !!

fonant’s picture

fonant commented

I found that this worked to enable a re-install after an uninstall of commerce_shipping-7.x-1.0-dev:

DELETE FROM field_config WHERE field_name = 'shipping_method';
DROP TABLE field_data_shipping_method;
DROP TABLE field_revision_shipping_method;
vasike’s picture

vasike
Location Ramnicu Valcea
commented
Category: feature » bug

subscribe. it seems the module hasn't the uninstall

vasike’s picture

vasike
Location Ramnicu Valcea
commented
Title: How to delete the shipping module » Uninstall the module
Priority: Normal » Critical
googletorp’s picture

googletorp commented
Priority: Critical » Normal
googletorp’s picture

googletorp commented

I have given this some thought.

Commerce shipping stores a bit of persistant data:

• A field on the shipping line item type
• Rules

We could delete the fields on the shipping line items, but that wouldn't serve any purpose. If there are orders with shipping line items, there is no reason to delete the fields on those line items, as it would delete order information. These will be delete by the line item module when it is uninstalled anyways.

The rules should be deleted, which are done in the most resent patch committed.

I'm marking this as fixed. If some one can argue why this should be different, I'll take a look at this again.

vasike’s picture

vasike
Location Ramnicu Valcea
commented

Uninstall means delete all data & settings that are related with the installation. so i think this is not fixed

googletorp’s picture

googletorp commented
Status: Active » Fixed

#7 I have designed it to work like it does for the above reasons (#6). You are welcome to disagree, but unless you can argue why it should be different, please don't change status.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

vasike’s picture

vasike
Location Ramnicu Valcea
commented
Status: Closed (fixed) » Active

There is an installation error after the uninstall

FieldException: Attempt to create an instance of field shipping_method on bundle shipping that already has an instance of that field. în field_create_instance() (linia 486 din D7_path/modules/field/field.crud.inc).

googletorp’s picture

googletorp commented
Status: Active » Fixed

I have committed a fix to dev : http://drupal.org/commitlog/commit/18412/fa4708e4d2f5713acaab7abf8c5bb11...

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.