Timeline for What is the proper way to uninstall a module that adds a content type
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 22, 2013 at 9:29 | vote | accept | MyNameIsStain | ||
| May 22, 2013 at 9:14 | history | edited | Mołot | CC BY-SA 3.0 |
added 251 characters in body
|
| May 22, 2013 at 9:12 | comment | added | MyNameIsStain | Ok thank you. I currently remove all nodes of this type in my hook_uninstall but the content type remains in db. | |
| May 22, 2013 at 9:10 | comment | added | Mołot | Yes it is - if you have any content of that content type, or if for some other reason Drupal "thinks" it may be unclean to remove it entirely. Of course you are allowed to force-delete it, but then you are responsible for all the cleaning that is needed. | |
| May 22, 2013 at 9:07 | comment | added | MyNameIsStain | So you say I should not use node_type_delete in hook_uninstall (in file .install) if I have hook_node_info in .module? Because now I use hook_node_info and I create fields and instances in hook_install but I don't use node_type_save. And in hook_uninstall I take care of removing previously created fields and instances. But the thing is when I uninstall the module, the content type remains in node_type table but it is now disabled. Is this the normal behavior? | |
| May 22, 2013 at 8:55 | history | edited | Mołot | CC BY-SA 3.0 |
added 383 characters in body
|
| May 22, 2013 at 8:11 | history | answered | Mołot | CC BY-SA 3.0 |